Skip to content

Fix protected publish for v3 layout buildcaches #1099

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

scottwittenburg
Copy link
Collaborator

Updates the v3 version of protected publish to correctly look for manifests, generating the meta and archive urls from those.

I tested this by publishing a single test stack (build_systems) to the root under both v2 and v3 layouts. We should be able to merge it now, and publishing v2 stacks to the root will continue to work. Once the content-addressable tarballs PR is merged to spack develop, we will need a tiny PR to the cron job arguments to swtich from --version 2 to --version 3.

Updates the v3 version of protected publish to correctly look for
manifests, generating the meta and archive urls from those.
@scottwittenburg
Copy link
Collaborator Author

Not sure it makes sense to update the image version in the migrate job, since we're not planning to update that for the newest v3 layout.

@scottwittenburg scottwittenburg merged commit 1d1044c into spack:main Apr 23, 2025
14 of 15 checks passed
@scottwittenburg scottwittenburg deleted the fix-protected-publish-v3 branch April 23, 2025 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants