Speed up JLL registration jobs - #14504
Open
maleadt wants to merge 3 commits into
Open
Conversation
Upload BinaryBuilder’s per-tarball metadata alongside build artifacts and pass it to the registration job outside the release-asset directory. Older builds remain supported through BinaryBuilder’s inspection fallback. Run registration with eight Julia threads. Clear both publication tokens while instantiating dependencies and regenerating recipe metadata.
Use a global Buildkite concurrency gate to admit three registration builds at once, while a per-package concurrency group prevents simultaneous wrapper-version selection for the same JLL. Cap each ghr process at four uploads so aggregate release-upload concurrency remains bounded.
maleadt
marked this pull request as draft
August 21, 2026 13:23
maleadt
marked this pull request as ready for review
August 21, 2026 17:17
Member
|
Might want to bump the version number of HelloWorldC, to test that the updated pipeline works when this is merged |
giordano
approved these changes
Aug 21, 2026
giordano
left a comment
giordano
left a comment
Member
There was a problem hiding this comment.
Haven't reviewed in detail, but at high level looks good
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
2 participants
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.
Pass BinaryBuilder's per-tarball metadata from build jobs to the registration pipeline, allowing registration to reuse hashes and product locations computed while packaging.
Metadata sidecars are uploaded as Buildkite artifacts but downloaded into a directory separate from the tarballs, so they are not published as GitHub release assets. Builds without sidecars continue to use
BinaryBuilder's tarball-inspection fallback.
Registration now starts Julia with eight threads so the fallback can inspect multiple platforms concurrently.
The registration pipeline also uses a Buildkite concurrency gate:
ghrprocess is capped at four concurrent uploads.This reduces organization-wide queueing without allowing simultaneous wrapper-version selection for the same JLL or unbounded GitHub API traffic.
Requires JuliaPackaging/BinaryBuilderBase.jl#489 and JuliaPackaging/BinaryBuilder.jl#1446