Make release Job Take Inputs From Multi-Target Deployments

[CodeGat]

We don't want a Release made from every deployment - instead, we would like to merge information from all the deployment targets when making a release.

[CodeGat]

In that case, what happens if the versions diverge?

For example, what if we needed to fix up something on one target, but not the other? Should they both be bumped, and only one of them released? Should we have a release per target? Hm.......

[CodeGat]

On Zulip, we discussed different options for this release pipeline, and we noted:

Option 1: Have a single model version across HPCs
This would mean that the version of a model would be shared between HPCs. For example, both Gadi and Setonix deployments would share a GitHub Release of 2025.01.0, and have the same version. But this creates problems if a model requires changes for only one HPC.

Option 2: Versions of a model can vary based on HPC
This would mean that we create GitHub Releases for a particular HPC target, rather than overall. For example, there could be a GitHub Release for Gadi at 2025.01.0, and a different GitHub Release for Setonix at 2025.01.1. This might be confusing for users to see that there are releases for different environments.

Option 3: Have a canonical HPC target and version at Gadi, and the other HPCs are just a bonus
This would mean that we do things as we do it now, having a Release artifact for Gadi, but we deploy to other HPCs as a bonus.

And am currently considering Option 1 for majors, and Option 2 for minors, potentially.

[CodeGat]

After a conversation with @aidanheerdegen - we note that we will just go with Option 1. In the case where one deployment target needs a fix that the other one doesn't, the other will essentially have the same contents as the minor version.

[CodeGat]

Old Release Notes (minus autogenerated section)

This release of access-om2 2024.03.0 uses spack-packages 2024.03.22 and spack-config 2024.03.22.

[CodeGat]

New Release Notes (minus autogenerated section)

This is an official release of access-om2 2024.03.0.

Deployment Information

Gadi

Deployed using spack 0.22, spack-packages 2024.03.22 and spack-config 2024.03.22.
Deployed as module accessible using:

module use /g/data/vk83/modules
module load access-om2/2024.03.0

Setonix

Deployed using spack 0.22, spack-packages 2024.03.22 and spack-config 2024.03.22.
Deployed as module accessible using:

module use /some/other/modules
module load access-om2/2024.03.0