@@ -69,7 +69,7 @@ This workflow handles building and running short CI tests on a given spack manif
6969``` yaml
7070jobs :
7171 test :
72- uses : access-nri/build-ci/.github/workflows/ci.yml@v2
72+ uses : access-nri/build-ci/.github/workflows/ci.yml@v3
7373 with :
7474 spack-manifest-path : .github/build/spack.yaml.j2
7575` ` `
7979` ` ` yaml
8080jobs :
8181 test :
82- uses : access-nri/build-ci/.github/workflows/ci.yml@v2
82+ uses : access-nri/build-ci/.github/workflows/ci.yml@v3
8383 with :
8484 spack-manifest-path : .github/build/spack.yaml.j2
8585 spack-manifest-data-path : .github/build/data/data.json
@@ -109,7 +109,7 @@ jobs:
109109 - .github/build/one.spack.yaml.j2
110110 - .github/build/two.spack.yaml.j2
111111 - .github/build/three.spack.yaml.j2
112- uses : access-nri/build-ci/.github/workflows/ci.yml@v2
112+ uses : access-nri/build-ci/.github/workflows/ci.yml@v3
113113 with :
114114 spack-manifest-path : ${{ matrix.manifest }}
115115` ` `
@@ -129,7 +129,7 @@ jobs:
129129 compiler : .github/build/compiler/intel.spack.yaml
130130 - manifest : .github/build/two.spack.yaml.j2
131131 compiler : .github/build/compiler/gcc.spack.yaml
132- uses : access-nri/build-ci/.github/workflows/ci.yml@v2
132+ uses : access-nri/build-ci/.github/workflows/ci.yml@v3
133133 with :
134134 spack-manifest-path : ${{ matrix.values.manifest }}
135135 spack-compiler-manifest-path : ${{ matrix.values.compiler }}
@@ -147,7 +147,7 @@ jobs:
147147 # This would be a combination of all defined manifest/compilers (eg, 4 jobs)
148148 manifest : [".github/build/one.spack.yaml.j2", ".github/build/two.spack.yaml.j2"]
149149 compiler : [".github/build/compiler/intel.spack.yaml", ".github/build/compiler/gcc.spack.yaml"]
150- uses : access-nri/build-ci/.github/workflows/ci.yml@v2
150+ uses : access-nri/build-ci/.github/workflows/ci.yml@v3
151151 with :
152152 spack-manifest-path : ${{ matrix.values.manifest }}
153153 spack-compiler-manifest-path : ${{ matrix.values.compiler }}
@@ -177,7 +177,7 @@ The jinja data file (and the jinja-templatable spack manifest) can be much more
177177Alternatively, you can supply a newline-separated list of space-separated template-value pairs through `inputs.spack-manifest-data-pairs`, which are more useful if you are supplying data to this workflow through `need`ed job outputs. For example :
178178
179179` ` ` yaml
180- uses: access-nri/build-ci/.github/workflows/ci.yml@v2
180+ uses: access-nri/build-ci/.github/workflows/ci.yml@v3
181181 with:
182182 spack-manifest-path: .github/build-ci/manifests/spack.yaml.j2
183183 spack-manifest-data-pairs: |-
@@ -232,7 +232,7 @@ jobs:
232232 file:
233233 - .github/build-ci/manifests/some.spack.yaml.j2
234234 - .github/build-ci/manifests/another.spack.yaml.j2
235- uses: access-nri/build-ci/.github/workflows/ci.yaml@v2
235+ uses: access-nri/build-ci/.github/workflows/ci.yaml@v3
236236 with:
237237 spack-manifest-path: ${{ matrix.file }}
238238
0 commit comments