Conversation
3555cc3 to
8fe8066
Compare
|
🚀 Attempted to deploy 🖥️
|
64bf7d9 to
c5293fe
Compare
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
b30738a to
a2c6bee
Compare
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
References issue ACCESS-NRI/build-cd#313 and PR ACCESS-NRI/build-cd#326
References rollout issue ACCESS-NRI/build-cd#328
References project Spack `0.22` to `1.0` Migration
Important
This PR is a major update to the deployment 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 deployments to
spack < 1.0.If you want to deploy to instances of
spack < 1.0, you must usebuild-cd < v8.If you want to deploy to instances of
spack >= 1.0, you must usebuild-cd >= v8.Background
We are moving on up to
spack v1! This update to spack contains many bug fixes, optimisations and new features that can be incorporated intobuild-cd.This update also contains changes that make
spack v0.Xincompatible with thisbuild-cd v8update - the most prominent one being the splitting of spacks core codebase from it's builtin spack-packages repo. This means that for provenance, one to keep track of bothbuiltinspack-packages and our own, renamedaccess-spack-packages.build-cdwill centrally control the version of builtinspack-packagesfor a given instance, andconfig/versions.jsonsspack-packageskey is renamed toaccess-spack-packages.As noted earlier, this major version of
build-cdcan only supportspack v1, due tospack v1-specific commands in the infrastructure. If you still want to deploy tospack v0.X, you will need to changebuild-cdtov7, and update theconfig/versions.jsonfile/spack.yaml.Features
Prerequisites for Merging
build-cdentrypoints (this PR!)config/versions.jsonwith new inputs (also this PR!)spack v1🚀 The latest prerelease
coastri-roms/pr6-8at 53aa13d is here: #6 (comment) 🚀