Skip to content

Commit 08d3e9a

Browse files
committed
Update spack/README.
1 parent de520ae commit 08d3e9a

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

buildsystem/spack/README.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,11 +22,15 @@ any existing installations unusable due to changes in the hashing algorithm.
2222

2323
## Using the automatic pipelines in GitLab PRs
2424

25-
Spack modules are automatically rebuilt via CI pipelines for a cluster when a commit message includes `[<clustername>-rebuild]` where `<clustername>` is one of the following [newell, deception, ascent].
25+
There are currently no clusters supporting automatic builds via CI pipelines.
2626

27-
See the [developer guidelines](../../docs/developer_guidelines.md) for a general workflow outline.
27+
Spack modules could be automatically rebuilt via CI pipelines for a cluster when a commit message
28+
includes `[<clustername>-rebuild]`. See the [developer guidelines](../../docs/developer_guidelines.md)
29+
for a general workflow outline. Once a build is finished, a new commit is pushed to the branch
30+
with a commit message with `[<clustername>-test]`, where tests are run only for that platform.
31+
If you want all of CI to be re-run after a specific platform test, you may have to push another
32+
empty commit, or re-run CI manually.
2833

29-
Once a build is finished, a new commit is pushed to the branch with a commit message with `[<clustername>-test]`, where tests are run only for that platform. If you want all of CI to be re-run after a specific platform test, you may have to push another empty commit, or re-run CI manually.
3034
## General Workflow
3135

3236
Run scripts in the following order to install using spack for a supported platform.
@@ -124,7 +128,7 @@ in `configure_modules.sh` that aligns with that is specified in the environment.
124128
These modules are used in `buildsystem/<build_type>/` in various scripts for each
125129
platform, and you should ensure these are compatible with the module configuration
126130
used for each platform. Make sure to create variable files that are consistent
127-
with examples for `gcc-cuda/newell` and `clang-hip/frontier`.
131+
with examples for `clang-hip/frontier`.
128132

129133
If you have an update in the ExaGO/HiOp spack package, you might need to update
130134
the relevant `spack.yaml` and configure module scripts for each platform.

0 commit comments

Comments
 (0)