Add BB2 CI setup#13498
Draft
staticfloat wants to merge 4 commits intomasterfrom
Draft
Conversation
staticfloat
force-pushed
the
sf/bb2
branch
7 times, most recently
from
b8dfcfd to
655104f
Compare
staticfloat
force-pushed
the
sf/bb2
branch
7 times, most recently
from
b3dc8a2 to
fbea901
Compare
This adds a parallel CI setup that runs BinaryBuilder2 builds. The basic flow is similar to that of BB1 builds, with the exception that build selection is more finegrained than just per-platform (e.g. `build_tarballs.jl <platform>`) and instead uses BuildConfig spec hashes to determine which builds and extractions to perform. Existing BB1 and BB2 projects can both be built within a single PR, however BB2 projects can only depend on other BB2 projects (they require metadata that is created only by BB2).
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This adds a parallel CI setup that runs BinaryBuilder2 builds.
The basic flow is similar to that of BB1 builds, with the exception that
build selection is more finegrained than just per-platform (e.g.
build_tarballs.jl <platform>) and instead uses BuildConfig spechashes to determine which builds and extractions to perform.
Existing BB1 and BB2 projects can both be built within a single PR,
however BB2 projects can only depend on other BB2 projects (they require
metadata that is created only by BB2).