Closed aidanheerdegen closed 1 month ago
Once we have the ability to utilise module load model/version in payu configurations
module load model/version
payu
https://github.com/ACCESS-NRI/model-config-tests/issues/10
we should have a QA configuration check that compares the executable paths in manifests/exe.yaml and check they match an install path in the spack.locations.json release artefact for the relevant model version
manifests/exe.yaml
spack.locations.json
https://github.com/ACCESS-NRI/build-cd/issues/51
The release is available at a predictable URL for a given model version, e.g.
https://github.com/ACCESS-NRI/ACCESS-OM2/releases/tag/2024.03.0
and the relevant artefact is just a path added to that url, e.g.
https://github.com/ACCESS-NRI/ACCESS-OM2/releases/download/2024.03.0/spack.location
(note that spack.location.json was not generated for the above release, but will be available in the future)
spack.location.json
Once we have the ability to utilise
module load model/versioninpayuconfigurationshttps://github.com/ACCESS-NRI/model-config-tests/issues/10
we should have a QA configuration check that compares the executable paths in
manifests/exe.yamland check they match an install path in thespack.locations.jsonrelease artefact for the relevant model versionhttps://github.com/ACCESS-NRI/build-cd/issues/51
The release is available at a predictable URL for a given model version, e.g.
https://github.com/ACCESS-NRI/ACCESS-OM2/releases/tag/2024.03.0
and the relevant artefact is just a path added to that url, e.g.
https://github.com/ACCESS-NRI/ACCESS-OM2/releases/download/2024.03.0/spack.location
(note that
spack.location.jsonwas not generated for the above release, but will be available in the future)