Skip to content

Use access.nri.ci.user scope for runner image, access.nri.admin scope for upstream#301

Merged
CodeGat merged 6 commits into
v3from
spack-config-new-user-scope
May 1, 2026
Merged

Use access.nri.ci.user scope for runner image, access.nri.admin scope for upstream#301
CodeGat merged 6 commits into
v3from
spack-config-new-user-scope

Conversation

@CodeGat

@CodeGat CodeGat commented Apr 22, 2026

Copy link
Copy Markdown
Member

References ACCESS-NRI/spack-config#114

Background

Admins should have configuration as a sibling directory to the spack instance. Users should have configuration under their home directory.

In build-cis case, upstream images are admin, runner images are regular users.

The PR

  • Update Dockerfiles upstream target to use --scope=access.nri.admin
  • Update workflow and actions (using the runner) to use --scope=access.nri.ci.user
  • Update default spack ref to new access/releases/v1.1
  • Dockerfile: Move [SOURCE|ENV]_[COMPILERS|PACKAGES]_SPACK_MANIFEST ARGs/ENVs into the stage they're relevant in - upstream!
  • compose: Split variables down more

Testing

Tested in ACCESS-NRI/access-test-component#21 via https://github.com/ACCESS-NRI/access-test-component/actions/runs/24810746757?pr=21, using runner image created by #301 (comment)

@CodeGat CodeGat added priority:high A high priority issue - has an impact on core functionality type:enhancement improvements to code but not new features version:PATCH Requires a change to the patch version - bug fixes labels Apr 22, 2026
@CodeGat CodeGat self-assigned this Apr 22, 2026
@CodeGat CodeGat added priority:high A high priority issue - has an impact on core functionality type:enhancement improvements to code but not new features version:PATCH Requires a change to the patch version - bug fixes labels Apr 22, 2026
@github-actions

Copy link
Copy Markdown

Image at spack-config-new-user-scope had build status success and push status success. If successful, image can be found in https://github.com/orgs/ACCESS-NRI/packages?tab=packages&q=build-ci-. See details at https://github.com/ACCESS-NRI/build-ci/actions/runs/24808802710

@CodeGat CodeGat force-pushed the spack-config-new-user-scope branch from 9e79b3b to 13d8ad6 Compare April 23, 2026 01:08
@CodeGat CodeGat marked this pull request as ready for review April 23, 2026 01:08
@CodeGat CodeGat requested a review from harshula April 23, 2026 01:08
@CodeGat CodeGat changed the title Use access.nri.ci.user scope for runner image, access.nri.admin scope for upstream Use access.nri.ci.user scope for runner image, access.nri.admin scope for upstream Apr 23, 2026
harshula
harshula previously approved these changes Apr 23, 2026

@harshula harshula left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Thanks!

@harshula

Copy link
Copy Markdown
Collaborator

Hi @CodeGat , Do you want to set SPACK_USER_CACHE_PATH in the Dockerfile in this PR?

…`, others to `$spack/../runner/spack-user-cache`
@CodeGat

CodeGat commented Apr 23, 2026

Copy link
Copy Markdown
Member Author

Done in 4c45084 @harshula

@CodeGat CodeGat marked this pull request as draft April 29, 2026 04:20
@CodeGat CodeGat removed the request for review from harshula April 29, 2026 04:20
@github-actions

Copy link
Copy Markdown

Image at spack-config-new-user-scope had build status failure and push status skipped. If successful, image can be found in https://github.com/orgs/ACCESS-NRI/packages?tab=packages&q=build-ci-. See details at https://github.com/ACCESS-NRI/build-ci/actions/runs/25090744434

@CodeGat CodeGat force-pushed the spack-config-new-user-scope branch from cae5012 to 330c63f Compare April 29, 2026 04:34
@github-actions

Copy link
Copy Markdown

Image at spack-config-new-user-scope had build status failure and push status skipped. If successful, image can be found in https://github.com/orgs/ACCESS-NRI/packages?tab=packages&q=build-ci-. See details at https://github.com/ACCESS-NRI/build-ci/actions/runs/25091097124

@CodeGat CodeGat force-pushed the spack-config-new-user-scope branch from 330c63f to 0334a15 Compare April 29, 2026 04:47
@github-actions

Copy link
Copy Markdown

Image at spack-config-new-user-scope had build status failure and push status skipped. If successful, image can be found in https://github.com/orgs/ACCESS-NRI/packages?tab=packages&q=build-ci-. See details at https://github.com/ACCESS-NRI/build-ci/actions/runs/25091441459

@CodeGat CodeGat force-pushed the spack-config-new-user-scope branch from 0334a15 to cf8cc30 Compare April 29, 2026 04:59
@CodeGat CodeGat force-pushed the spack-config-new-user-scope branch from cf8cc30 to b86eef5 Compare April 29, 2026 05:02
@github-actions

Copy link
Copy Markdown

Image at spack-config-new-user-scope had build status success and push status success. If successful, image can be found in https://github.com/orgs/ACCESS-NRI/packages?tab=packages&q=build-ci-. See details at https://github.com/ACCESS-NRI/build-ci/actions/runs/25091814321

@CodeGat

CodeGat commented Apr 29, 2026

Copy link
Copy Markdown
Member Author

Noting that the above image was built correctly, and worked when building access-test-component: https://github.com/ACCESS-NRI/access-test-component/actions/runs/25093186453?pr=22 @harshula

@CodeGat CodeGat force-pushed the spack-config-new-user-scope branch from b86eef5 to b08578b Compare April 29, 2026 06:19
@CodeGat CodeGat marked this pull request as ready for review April 29, 2026 06:19
@CodeGat CodeGat requested a review from harshula April 29, 2026 06:20
@CodeGat CodeGat force-pushed the spack-config-new-user-scope branch from e3a88b1 to 1a79920 Compare April 30, 2026 05:03

@harshula harshula left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

🤞

@CodeGat CodeGat merged commit e9f41d5 into v3 May 1, 2026
2 checks passed
@CodeGat CodeGat deleted the spack-config-new-user-scope branch May 1, 2026 01:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority:high A high priority issue - has an impact on core functionality type:enhancement improvements to code but not new features version:PATCH Requires a change to the patch version - bug fixes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants