Make CI callable from remote repo #579
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JssDWt
force-pushed
the
ci-callable-from-remote-repo
branch
from
f07f7a9
to
47150c3
Compare
roeierez
approved these changes
Nov 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to compile the packages for different languages to use in breez-sdk-docs,it's useful to be able to compile the packages from there. However, when checking out the repository, by default it uses the repository of the caller repository. This PR makes it possible to build the sdk packages from a remote repository by making it possible to explicitly set the repository name (but not publish them).
Also this adds an option to the CI to create dummy binaries rather than real binaries. Building binaries can take a lot of time. If you only want to see the package structure for example, or you only want a package with proper language bindings, you can use dummy binaries to speed up the CI process. Like in breez-sdk-docs, we don't really need the runtime binaries, we just need the package structure with language bindings.
Goal is to support breez/breez-sdk-docs#81