Infra Update `v8`: `spack v1` Support by CodeGat · Pull Request #168 · ACCESS-NRI/ACCESS-ESM1.6

CodeGat · 2025-11-18T03:05:34Z

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

Note

This infrastructure update created a new Release, but it maintained reproducibility with the current main

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 use build-cd < v8.
If you want to deploy to instances of spack >= 1.0, you must use build-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 into build-cd.

This update also contains changes that make spack v0.X incompatible with this build-cd v8 update - 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 both builtin spack-packages and our own, renamed access-spack-packages. build-cd will centrally control the version of builtin spack-packages for a given instance, and config/versions.jsons spack-packages key is renamed to access-spack-packages.

As noted earlier, this major version of build-cd can only support spack v1, due to spack v1-specific commands in the infrastructure. If you still want to deploy to spack v0.X, you will need to change build-cd to v7, and update the config/versions.json file/spack.yaml.

Features

Support for spack v1: We're moving to a new, non-beta version of spack! It contains bug fixes, features and optimisations over the old version.
No more spack.config!: This is now handled in spack-config via the .custom-scopes key in config/versions.json!

Prerequisites for Merging

Update build-cd entrypoints (this PR!)
Update config/versions.json with new inputs (also this PR!)
Validate compiler additions to the spack manifest (this PR, too!)
Test and Verify Model built with spack v1

🚀 The latest prerelease access-esm1p6/pr168-6 at 97f59c0 is here: #168 (comment) 🚀

🚀 The latest prerelease access-esm1p6/pr168-7 at 34f23bd is here: #168 (comment) 🚀

CodeGat · 2026-01-05T05:19:46Z

Note: Rebased all the changes from the v6/v7 infra updates, so this should be good to go once the linked build-cd PRs are done.

github-actions · 2026-02-12T01:16:44Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr168-1 with commit 4cd0d7f

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-esm1.6, defined in spack.yaml, will be deployed to Gadi as:

2026.01.000 as a Release (when merged).
pr168-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr168-1

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/1.1/spack in the access-esm1p6-pr168-1 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 1.1
spack/spack-packages version 8ed34337e15d759890b68682d704aa55dd243537
access-nri/access-spack-packages version 2026.02.002
access-nri/spack-config version 2026.02.001

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

CodeGat · 2026-02-12T02:55:57Z

Although it installed fine, it failed to get the metadata from the restricted directory. I'll fix up this bug now.

Edit: Fixed via ACCESS-NRI/build-cd#357

github-actions · 2026-02-12T05:24:08Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr168-2 with commit 137da68

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-esm1.6, defined in spack.yaml, will be deployed to Gadi as:

2026.01.000 as a Release (when merged).
pr168-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr168-2

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/1.1/spack in the access-esm1p6-pr168-2 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 1.1
spack/spack-packages version 8ed34337e15d759890b68682d704aa55dd243537
access-nri/access-spack-packages version 2026.02.002
access-nri/spack-config version 2026.02.001

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

github-actions · 2026-02-12T05:29:51Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr168-3 with commit b51aa55

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-esm1.6, defined in spack.yaml, will be deployed to Gadi as:

2026.01.000 as a Release (when merged).
pr168-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr168-3

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/1.1/spack in the access-esm1p6-pr168-3 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 1.1
spack/spack-packages version 8ed34337e15d759890b68682d704aa55dd243537
access-nri/access-spack-packages version 2026.02.002
access-nri/spack-config version 2026.02.001

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

CodeGat · 2026-02-12T05:34:57Z

The above deployment was successful (as was the metadata generation).

CodeGat · 2026-02-13T04:30:10Z

!update-configs

github-actions · 2026-02-13T04:31:21Z

🔧 Opening Model Configuration PRs in ACCESS-NRI/access-esm1.6-configs

Configurations Requested

Configurations requested from profile default:

dev-1pctCO2
dev-4xCO2+concentrations
dev-historical+concentrations
dev-preindustrial+concentrations

Pull Requests Opened

The following PRs were opened:

More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-ESM1.6/actions/runs/21974705756

github-actions · 2026-02-18T01:21:27Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr168-4 with commit 0d8b7df

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-esm1.6, defined in spack.yaml, will be deployed to Gadi as:

2026.01.000 as a Release (when merged).
pr168-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr168-4

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/1.1/spack in the access-esm1p6-pr168-4 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 1.1
spack/spack-packages version 39aeb9dbcc13b6a53e40c77b672c397e1f4c93ec
access-nri/access-spack-packages version 2026.02.002
access-nri/spack-config version 2026.02.001

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

CodeGat · 2026-02-18T01:21:47Z

!update-configs

github-actions · 2026-02-18T01:22:50Z

🔧 Opening/Updating Model Configuration PRs in ACCESS-NRI/access-esm1.6-configs

Configurations Requested

Configurations requested from profile default:

dev-1pctCO2
dev-4xCO2+concentrations
dev-historical+concentrations
dev-preindustrial+concentrations

Pull Requests Opened/Updated

The following PRs were opened/updated:

More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-ESM1.6/actions/runs/22122642995

blimlim · 2026-03-02T23:18:10Z

@manodeep and @harshula too!

CodeGat · 2026-03-02T23:19:17Z

Yes, thanks @harshula, @manodeep as well!

I've just rebased the branch so it is ready for a proper merge now.

blimlim

Less familiar with the CI/CD side, but the spack.yaml looks good to me!

manodeep

I am not across the CI/CD bits, but everything looks fine.

Only thing might be to see if you could separate out the white-space-only changes in a different PR?

CodeGat · 2026-03-03T02:24:27Z

Thanks @manodeep ! We might need for it to be in this one just so it's compatible with the formatter in spack v1.1

anton-seaice · 2026-03-03T22:05:46Z

Extract from the concretisation:

[+]  vjfi7jq          ^netcdf-c@4.9.2~blosc~byterange~dap~fsync~hdf4~jna~logging+mpi~nczarr_zip+optimize~parallel-netcdf+pic~shared~szip~zstd build_system=autotools patches:=0161eb8 platform=linux os=rocky8 target=x86_64_v2 %c=oneapi@2025.2.0
[+]  bzfhqsh              ^hdf5@1.14.3~cxx~fortran+hl~ipo~java~map+mpi+shared~subfiling~szip~threadsafe+tools api=default build_system=cmake build_type=Release generator=make patches:=82088c8,f42732a platform=linux os=rocky8 target=x86_64_v2 %c=oneapi@2025.2.0
[+]  rt6agvu                  ^pkgconf@2.5.1 build_system=autotools platform=linux os=rocky8 target=x86_64_v2 %c=oneapi@2025.2.0
[+]  uupdcdj                  ^zlib-ng@2.3.2+compat~new_strategies+opt+pic+shared build_system=autotools platform=linux os=rocky8 target=x86_64_v2 %c,cxx=oneapi@2025.2.0
[+]  ykcgsfm          ^netcdf-fortran@4.6.1~doc+pic+shared build_system=autotools platform=linux os=rocky8 target=x86_64_v2 %c,fortran=oneapi@2025.2.0

We should try setting

target=x86_64_v4 for netcdf-c and netcdf-fortran, but lets wait for the spack upstream meeting today to see what they say first

CodeGat · 2026-03-04T01:57:28Z

Yeah Peter was confused as well. Maybe we should set the target explicitly for netcdf-[c|fortran]

github-actions · 2026-03-04T03:22:35Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr168-7 with commit 34f23bd

🖥️ `Gadi` Deployment ❌

anton-seaice · 2026-03-04T03:39:16Z

1. Cannot find compatible targets for oasis3-mct and netcdf-fortran

Seems like spack enforces targets are the same or more flexible for dependencies then ?

CodeGat · 2026-03-04T04:18:56Z

I guess I should drop that change, then

anton-seaice · 2026-03-04T04:58:06Z

I guess with are stuck with the spack set targets for those packages

CodeGat · 2026-03-04T05:16:40Z

Okay it's like nothing ever happened 😆 approve away

anton-seaice

Thanks @CodeGat ! adn @blimlim

CodeGat added the type:infra Related to CI/CD label Nov 18, 2025

CodeGat self-assigned this Nov 18, 2025

CodeGat force-pushed the infra-update-v8 branch from 785d31c to 63c29d0 Compare January 5, 2026 05:18

CodeGat force-pushed the infra-update-v8 branch from 9966fac to 9fb51d0 Compare February 11, 2026 22:26

ACCESS-NRI deleted a comment from github-actions Bot Feb 12, 2026

CodeGat temporarily deployed to Gadi Prerelease February 12, 2026 00:36 — with GitHub Actions Inactive

CodeGat temporarily deployed to Gadi Prerelease February 12, 2026 05:19 — with GitHub Actions Inactive

CodeGat marked this pull request as ready for review February 12, 2026 05:20

CodeGat temporarily deployed to Gadi Prerelease February 12, 2026 05:26 — with GitHub Actions Inactive

CodeGat mentioned this pull request Feb 17, 2026

Spack v0.22 to v1.1.x migration plan ACCESS-NRI/access-spack-packages#345

Open

CodeGat temporarily deployed to Gadi Prerelease February 18, 2026 00:37 — with GitHub Actions Inactive

CodeGat and others added 4 commits March 3, 2026 10:17

TEST: Rerun after metadata fix in ACCESS-NRI/build-cd#357

efa1957

TEST: After updating the test branch

f28f8da

TEST: Redeploy after modulefile issues

60e3d49

[no ci] Set oasis3-mct target=x86_64_v2 for reproducibility

6b2308e

CodeGat force-pushed the infra-update-v8 branch from 97f59c0 to 6b2308e Compare March 2, 2026 23:18

CodeGat requested review from blimlim and manodeep March 2, 2026 23:19

blimlim previously approved these changes Mar 2, 2026

View reviewed changes

[no ci] Update version to 2026.02.001 for deployment

a6cdc34

CodeGat dismissed blimlim’s stale review via a6cdc34 March 2, 2026 23:50

CodeGat requested a review from anton-seaice March 3, 2026 00:15

manodeep reviewed Mar 3, 2026

View reviewed changes

manodeep previously approved these changes Mar 3, 2026

View reviewed changes

CodeGat dismissed manodeep’s stale review via b01dd3d March 4, 2026 03:13

ACCESS-NRI deleted a comment from github-actions Bot Mar 4, 2026

CodeGat had a problem deploying to Gadi Prerelease March 4, 2026 03:19 — with GitHub Actions Failure

CodeGat force-pushed the infra-update-v8 branch from 34f23bd to a6cdc34 Compare March 4, 2026 05:16

anton-seaice approved these changes Mar 4, 2026

View reviewed changes

CodeGat merged commit 0057628 into main Mar 4, 2026

CodeGat deleted the infra-update-v8 branch March 4, 2026 05:31

Conversation

CodeGat commented Nov 18, 2025 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Background

Features

Prerequisites for Merging

Uh oh!

CodeGat commented Jan 5, 2026

Uh oh!

github-actions Bot commented Feb 12, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

CodeGat commented Feb 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Feb 12, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions Bot commented Feb 12, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

CodeGat commented Feb 12, 2026

Uh oh!

CodeGat commented Feb 13, 2026

Uh oh!

github-actions Bot commented Feb 13, 2026

Uh oh!

github-actions Bot commented Feb 18, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

CodeGat commented Feb 18, 2026

Uh oh!

github-actions Bot commented Feb 18, 2026

Uh oh!

blimlim commented Mar 2, 2026

Uh oh!

CodeGat commented Mar 2, 2026

Uh oh!

blimlim left a comment

Choose a reason for hiding this comment

Uh oh!

manodeep left a comment

Choose a reason for hiding this comment

Uh oh!

CodeGat commented Mar 3, 2026

Uh oh!

anton-seaice commented Mar 3, 2026

Uh oh!

CodeGat commented Mar 4, 2026

Uh oh!

github-actions Bot commented Mar 4, 2026

🖥️ Gadi Deployment ❌

Uh oh!

anton-seaice commented Mar 4, 2026

Uh oh!

CodeGat commented Mar 4, 2026

Uh oh!

anton-seaice commented Mar 4, 2026

Uh oh!

CodeGat commented Mar 4, 2026

Uh oh!

anton-seaice left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

CodeGat commented Nov 18, 2025 •

edited by github-actions Bot

Loading

🖥️ `Gadi` Deployment ✔️

CodeGat commented Feb 12, 2026 •

edited

Loading

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ❌