Use access.nri.ci.user scope for runner image, access.nri.admin scope for upstream#301
Conversation
|
Image at spack-config-new-user-scope had build status |
9e79b3b to
13d8ad6
Compare
access.nri.ci.user scope for runner image, access.nri.admin scope for upstream
|
Hi @CodeGat , Do you want to set |
…`, others to `$spack/../runner/spack-user-cache`
|
Image at spack-config-new-user-scope had build status |
cae5012 to
330c63f
Compare
|
Image at spack-config-new-user-scope had build status |
330c63f to
0334a15
Compare
|
Image at spack-config-new-user-scope had build status |
0334a15 to
cf8cc30
Compare
…remove ACCESS_SPACK_ADMIN
cf8cc30 to
b86eef5
Compare
|
Image at spack-config-new-user-scope had build status |
|
Noting that the above image was built correctly, and worked when building |
b86eef5 to
b08578b
Compare
e3a88b1 to
1a79920
Compare
…ge SPACK_USER_CACHE_PATH to admin variant
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
Dockerfilesupstreamtarget to use--scope=access.nri.adminrunner) to use--scope=access.nri.ci.userspackref to newaccess/releases/v1.1[SOURCE|ENV]_[COMPILERS|PACKAGES]_SPACK_MANIFESTARGs/ENVsinto the stage they're relevant in -upstream!Testing
Tested in ACCESS-NRI/access-test-component#21 via https://github.com/ACCESS-NRI/access-test-component/actions/runs/24810746757?pr=21, using
runnerimage created by #301 (comment)