Conversation
CodeGat
force-pushed
the
infra-update-v3
branch
from
5c867f5 to
e2d5c2e
Compare
github-project-automation
bot
moved this to New Issues 🌅
in Spack `0.22` to `1.0` Migration
harshula
force-pushed
the
api-v2
branch
3 times, most recently
from
c163f27 to
f7a4cb5
Compare
harshula
force-pushed
the
api-v2
branch
8 times, most recently
from
4878de1 to
266d395
Compare
CodeGat
force-pushed
the
infra-update-v3
branch
from
2a4f94f to
8beef33
Compare
harshula
reviewed
Dec 9, 2025
harshula
reviewed
Dec 11, 2025
harshula
reviewed
Dec 11, 2025
Member
Author
|
@harshula I have updated this workflow to use the defaults from the called workflow by reading the defaults from the workflow itself. It's ready for review now! |
harshula
force-pushed
the
api-v2
branch
4 times, most recently
from
2849be1 to
9c55156
Compare
harshula
force-pushed
the
api-v2
branch
5 times, most recently
from
58dedf3 to
f571b78
Compare
… default inputs.builtin-spack-packages-ref
CodeGat
force-pushed
the
infra-update-v3
branch
2 times, most recently
from
b843d1e to
93506d8
Compare
harshula
pushed a commit
that referenced
this pull request
Dec 19, 2025
infra: Update to v3, get default spack-config-ref/spack-ref from build-ci workflow, use default container-image-version
harshula
pushed a commit
that referenced
this pull request
Jan 28, 2026
infra: Update to v3, get default spack-config-ref/spack-ref from build-ci workflow, use default container-image-version
harshula
pushed a commit
that referenced
this pull request
Feb 6, 2026
infra: Update to v3, get default spack-config-ref/spack-ref from build-ci workflow, use default container-image-version
harshula
pushed a commit
that referenced
this pull request
Feb 6, 2026
infra: Update to v3, get default spack-config-ref/spack-ref from build-ci workflow, use default container-image-version
harshula
pushed a commit
that referenced
this pull request
Feb 9, 2026
infra: Update to v3, get default spack-config-ref/spack-ref from build-ci workflow, use default container-image-version
harshula
pushed a commit
that referenced
this pull request
Feb 10, 2026
infra: Update to v3, get default spack-config-ref/spack-ref from build-ci workflow, use default container-image-version
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.
References issue ACCESS-NRI/build-ci#231 and PR ACCESS-NRI/build-ci#253
References project Spack `0.22` to `1.0` Migration
Important
This PR is a major update to the infrastructure. See below for the prerequisites for this repository to be able to merge this PR.
Important
This major version change marks the end of major infrastructure updates for CI using
spack < 1.0. They will still get bug fixes and non-breaking features if required.If you want to deploy to instances of
spack < 1.0, you must usebuild-ci v2.If you want to deploy to instances of
spack >= 1.0, you must usebuild-ci v3.Background
We are looking to transition
build-citov3! This is due to a migration tospack v1.X, fromv0.X, which offers many bug fixes, features, and optimisations.One of these changes is the splitting of spacks core codebase from the builtin spack-packages repository, which means that we have another lever to tweak for our builds: the version of
spack,spack-config, ourspack-packagesand the (new!) builtinspack-packages.Since we want to leave open the possibility of forking the builtin
spack-packages, we have also decided to renameACCESS-NRI/spack-packagestoACCESS-NRI/access-spack-packages. See #295 for more info.Therefore this is a major version update, as there are the following changes to the inputs (and analogous changes to the workflow outputs):
spack-packages-refinput, which defaulted tomain(in future,api-v1).access-spack-packages-refinput, which defaults to theapi-v2branch.builtin-spack-packages-refinput, which defaults to themainbranch.This means that:
container-image-version: :rocky-0.22-*, orspack-ref<releases/1.0, you must stay onv2due to the input changes.container-image-version: :rocky-1.*-*, orspack-ref>=releases/1.0, you must migrate tov3due to the input changes.It is possible to test across these versions of
spackif required, via a mix of workflow versions. Ask @CodeGat if you need this functionality.Features
The main new features include:
spack-packagesrepository, as well as our ownaccess-spack-packagesrepository. All of the bugfixes, features and optimisations added since0.22are available to us for future inclusion intobuild-ci.Prerequisites for Merging
build-cientrypoints tov3(this PR!)v3infra