Support content addressable buildcache#1058
Merged
scottwittenburg merged 19 commits intospack:mainfrom Feb 27, 2025
Merged
Conversation
scottwittenburg
commented
Feb 12, 2025
21 tasks
scottwittenburg
commented
Feb 14, 2025
zackgalbreath
requested changes
Feb 25, 2025
Collaborator
zackgalbreath
left a comment
There was a problem hiding this comment.
a couple questions and a couple typos, otherwise LGTM!
zackgalbreath
approved these changes
Feb 27, 2025
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.
Until spack has buildcache views, pipelines must be run pointing at independent mirrors, and
protected-publishis responsible for making stack-specific binaries available at the mirror root.Add support for "publishing" both old style as well as content addressable (
v2vsv3) buildcaches from stacks to the root. By default the script assumesv2layout, but it can be changed by adding--version <version>on the command line. The only accepted options are 2 and 3.Add an endpoint in the container that can migrate a binary mirror from the previous version to the content-addressed layout. Migration consists of, for each spec in the mirror: