Closed CodeGat closed 2 months ago
We have a good base for CI/CD with https://github.com/ACCESS-NRI/ACCESS-OM2/tree/main/.github/workflows. But this was done without knowing what pieces of the CI/CD are sufficiently generic for each new model. Using a new model will be a good test for how generic we can make certain aspects of the pipeline, which we can then add to https://github.com/ACCESS-NRI/build-cd
Some todos:
config
spack
If all of the models follow the same spack.yaml structure, this could be simplified massively. See drafted https://github.com/ACCESS-NRI/build-cd/pull/47
spack.yaml
We have a good base for CI/CD with https://github.com/ACCESS-NRI/ACCESS-OM2/tree/main/.github/workflows. But this was done without knowing what pieces of the CI/CD are sufficiently generic for each new model. Using a new model will be a good test for how generic we can make certain aspects of the pipeline, which we can then add to https://github.com/ACCESS-NRI/build-cd
Some todos:
config
spack
-based models easier