feat: use spack ci generate to setup build pipeline
Rather than having a single long build, we can split it up in different jobs with spack ci generate. This will be more resilient against failures. We can also run the builds inside a regular job instead of inside the container, and then only pull from the build cache once we build the container.
Merge request reports
Activity
assigned to @wdconinc
mentioned in merge request !411 (merged)
mentioned in merge request !412 (merged)
added 1 commit
- 140703a5 - fix: use internal tag for generate-pipelines image
added 5 commits
Toggle commit listadded 1 commit
- 048a3252 - fix: add required mappings for gitlab-ci section in spack.yaml
added 1 commit
- 3f7b44ba - fix: debug loading env; remove variables in spack.yaml
added 1 commit
- 082d31fd - fix: install python3-boto3 before generate-pipelines
added 15 commits
-
76284b4f - 1 commit from branch
master - f816f992 - feat: use spack ci generate to setup build pipeline
- 5208d483 - fix: use internal tag for generate-pipelines image
- 110392e8 - fix: disable automatic after_script docker
- ee45fc9b - fix: provide S3/AWS endpoint and access secrets to pipeline
- 42adf621 - fix: add required mappings for gitlab-ci section in spack.yaml
- 981252af - fix: move spack ci generate earlier
- d3c5848b - fix: use ORGREPO variables
- 3b181a4a - fix: debug loading env; remove variables in spack.yaml
- 17c4d475 - fix: install python3-boto3 before generate-pipelines
- 90aa7e0c - fix: apt-get update
- dd65f0fa - fix: no debug env; disable view
- 6a512d96 - fix: rm mirror spack-public
- c4bc339e - fix: list mirrors
- 6ca47de0 - fix: more attempts at ci generate debugging
Toggle commit list-
76284b4f - 1 commit from branch
Please register or sign in to reply