CI: 2025 10 31

Attendees

• Jacob Nesbitt
• John Parent
• Mike VanDenburgh
• Ryan Krattiger
• Tammy Dahlgren
• Todd Gamblin
• Zack Galbreath

Discussion Topics

• How best to update spack's CI module to enable separate test jobs for packages after they are built in our GitLab CI pipeliens.
• The need for a latest branch on spack-packages that represents the most recent commit of develop that passed all CI checks (including GitLab).
  • This will be used to minimize unnecessary failures when we re-enable GitLab CI pipelines for Spack core.
• We are preparing to create a new build cache for the upcoming v1.1 release of Spack.
  • We also plan to set up infrastructure to test newer versions of Spack (v1.1) against previous releases of spack-packages (2025.07).
• Todd shared his progress on updating how config scopes are managed in Spack (PR #51162).

Updates

• This week we performed an EKS upgrade for the cluster that hosts gitlab.spack.io.