Skip to content

Infra Update v8: spack v1 Support#19

Merged
CodeGat merged 10 commits intomainfrom
infra-update-v8
Feb 18, 2026
Merged

Infra Update v8: spack v1 Support#19
CodeGat merged 10 commits intomainfrom
infra-update-v8

Conversation

@CodeGat
Copy link
Member

@CodeGat CodeGat commented Nov 18, 2025

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 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.

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 mppnccombine-fast/pr19-13 at 58d7c16 is here: #19 (comment) 🚀

@CodeGat CodeGat self-assigned this Nov 18, 2025
@CodeGat CodeGat marked this pull request as ready for review February 15, 2026 23:20
@ACCESS-NRI ACCESS-NRI deleted a comment from github-actions bot Feb 15, 2026
@CodeGat CodeGat force-pushed the infra-update-v8 branch 2 times, most recently from b82c99e to d18bdc3 Compare February 15, 2026 23:30
@github-actions
Copy link

🚀 Attempted to deploy babeltrace2 Prerelease pr19-1 with commit d18bdc3

🖥️ Gadi Deployment ❌

@github-actions
Copy link

🚀 Attempted to deploy esmf Prerelease pr19-2 with commit d18bdc3

🖥️ Gadi Deployment ✔️

Usage Instructions

esmf, defined in esmf/spack.yaml, will be deployed to Gadi as:

  • v8.7.0 as a Release (when merged).
  • pr19-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load esmf/pr19-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 esmf-pr19-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:

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.

@harshula
Copy link
Collaborator

FYI, babeltrace2 was added to the upstream spack-packages: https://github.com/spack/spack-packages/blob/develop/repos/spack_repo/builtin/packages/babeltrace2/package.py

@github-actions
Copy link

🚀 Attempted to deploy fre-nctools Prerelease pr19-3 with commit d18bdc3

🖥️ Gadi Deployment ❌

@github-actions
Copy link

🚀 Attempted to deploy babeltrace2 Prerelease pr19-4 with commit ce16f6e

🖥️ Gadi Deployment ❌

@github-actions
Copy link

🚀 Attempted to deploy esmf Prerelease pr19-5 with commit ce16f6e

🖥️ Gadi Deployment ❌

@github-actions
Copy link

🚀 Attempted to deploy fre-nctools Prerelease pr19-6 with commit ce16f6e

🖥️ Gadi Deployment ✔️

Usage Instructions

fre-nctools, defined in fre-nctools/spack.yaml, will be deployed to Gadi as:

  • 2024.05-1 as a Release (when merged).
  • pr19-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load fre-nctools/pr19-6

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 fre-nctools-pr19-6 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:

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
Copy link

🚀 Attempted to deploy mppnccombine-fast Prerelease pr19-7 with commit ce16f6e

🖥️ Gadi Deployment ✔️

Usage Instructions

mppnccombine-fast, defined in mppnccombine-fast/spack.yaml, will be deployed to Gadi as:

  • 2025.07.000 as a Release (when merged).
  • pr19-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load mppnccombine-fast/pr19-7

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 mppnccombine-fast-pr19-7 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:

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
Copy link

🚀 Attempted to deploy babeltrace2 Prerelease pr19-8 with commit 54fdba5

🖥️ Gadi Deployment ❌

@github-actions
Copy link

🚀 Attempted to deploy esmf Prerelease pr19-9 with commit 54fdba5

🖥️ Gadi Deployment ❌

@github-actions
Copy link

🚀 Attempted to deploy babeltrace2 Prerelease pr19-10 with commit 58d7c16

🖥️ Gadi Deployment ❌

@harshula
Copy link
Collaborator

Hi @CodeGat , This PR can be merged with a failing babeltrace2.

There might be a missing dependency in an SPR:

In file included from plugins/lttng-utils/debug-info/bin-info.cpp:25:
plugins/lttng-utils/debug-info/bin-info.hpp:12:10: fatal error: elfutils/libdw.h: No such file or directory
 #include <elfutils/libdw.h>
          ^~~~~~~~~~~~~~~~~~
compilation terminated.

@github-actions
Copy link

🚀 Attempted to deploy esmf Prerelease pr19-11 with commit 58d7c16

🖥️ Gadi Deployment ✔️

Usage Instructions

esmf, defined in esmf/spack.yaml, will be deployed to Gadi as:

  • v8.7.0 as a Release (when merged).
  • pr19-11 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load esmf/pr19-11

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 esmf-pr19-11 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:

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
Copy link

🚀 Attempted to deploy fre-nctools Prerelease pr19-12 with commit 58d7c16

🖥️ Gadi Deployment ✔️

Usage Instructions

fre-nctools, defined in fre-nctools/spack.yaml, will be deployed to Gadi as:

  • 2024.05-1 as a Release (when merged).
  • pr19-12 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load fre-nctools/pr19-12

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 fre-nctools-pr19-12 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:

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 CodeGat deployed to Gadi Prerelease February 17, 2026 07:39 — with GitHub Actions Active
@github-actions
Copy link

🚀 Attempted to deploy mppnccombine-fast Prerelease pr19-13 with commit 58d7c16

🖥️ Gadi Deployment ✔️

Usage Instructions

mppnccombine-fast, defined in mppnccombine-fast/spack.yaml, will be deployed to Gadi as:

  • 2025.07.000 as a Release (when merged).
  • pr19-13 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load mppnccombine-fast/pr19-13

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 mppnccombine-fast-pr19-13 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:

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
Copy link
Member Author

CodeGat commented Feb 17, 2026

Given that we can go ahead with the failing babeltrace2, this is good to go!

@CodeGat CodeGat requested a review from harshula February 18, 2026 00:43
Copy link
Collaborator

@harshula harshula left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤞

@CodeGat CodeGat merged commit 0ca63e3 into main Feb 18, 2026
@CodeGat CodeGat deleted the infra-update-v8 branch February 18, 2026 03:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants