Repository navigation
Support reusing unchanged tarballs from an earlier JLL release - #1455
Merged
Merged
Conversation
maleadt
force-pushed
the
tb/partial-reuse
branch
from
October 16, 2026 08:04
4d8f380 to
33804d4
Compare
This was referenced Oct 16, 2026
Merged
Member
|
In https://github.com/JuliaPackaging/Yggdrasil/blob/910714b8c451f9d9058b57fe98e99dbc49848bdf/.ci/bb1_project/register_package.jl we already allow reusing binaries from previous releases with |
Member
Author
|
Right. |
The meta JSON describes sources, script, products and dependencies, but not the build_tarballs keyword arguments that also shape the tarballs (preferred_gcc_version, compilers, skip_audit, ...). Add them as build_options, so that CI can tell whether a platform's tarball from an earlier release is still what the recipe would build.
rebuild_jll_package gains reused_urls: tarballs that are not rebuilt but stay where an earlier release published them. Their Artifacts.toml entries keep that URL, and their metadata comes from the build metadata sidecar alone, so they need not be downloaded or re-uploaded. This lets Yggdrasil skip rebuilding platforms whose inputs did not change, e.g. the LLVM versions of the *_unified JLLs that a bump does not touch.
maleadt
force-pushed
the
tb/partial-reuse
branch
from
October 16, 2026 12:44
33804d4 to
afd3309
Compare
giordano
approved these changes
Oct 16, 2026
maleadt
added a commit
to JuliaPackaging/Yggdrasil
that referenced
this pull request
Oct 21, 2026
Picks up JuliaPackaging/BinaryBuilder.jl#1455 and JuliaPackaging/BinaryBuilderBase.jl#503, which the reuse of unchanged tarballs relies on.
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
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.
Yggdrasil rebuilds every platform of a recipe whenever the recipe changes. For the LLVM
*_unifiedJLLs, which carry all LLVM versions in one package, bumping one LLVM version rebuilt all 968 tarballs; 824 of them came out identical (same tree hash) to the previous release. That was ~35 of the 51 agent-hours of JuliaPackaging/Yggdrasil#15144.The plan is for Yggdrasil's CI to schedule only the platforms whose inputs changed, and to register the new JLL version with the unchanged platforms pointing at the tarballs of the earlier release. This PR adds what BinaryBuilder needs for that:
--meta-jsonrecords thebuild_tarballskeyword arguments that can affect the tarballs (preferred_gcc_version,compilers,skip_audit, ...) asbuild_options. Without them, two recipe versions with equal sources, script and dependencies could still produce different tarballs. Only explicitly passed options are recorded, and therepr-based values are only meant to be compared under the same Julia and BinaryBuilder versions.rebuild_jll_packageacceptsreused_urls: tarballs that are not rebuilt and stay where an earlier release published them. TheirArtifacts.tomlentries keep that URL, and their hashes and product paths come from the build metadata sidecar (read_build_meta(...; verify=false)), so they are neither downloaded nor re-uploaded. A platform that is both rebuilt and reused, or reused twice, is an error.Registration of
Clang_unifiedcurrently downloads and re-uploads 39 GB (25 min); with reuse that drops to the ~7 GB that actually changed.