d7405ddd39
Spack pipelines need to take specific actions internally that depend on whether the pipeline is being run on a PR to spack or a merge to the develop branch. Pipelines can also run in other repositories, which represents other possible use cases than just the two mentioned above. This PR creates a "SPACK_PIPELINE_TYPE" gitlab variable which is propagated to rebuild jobs, and is also used internally to determine which pipeline-specific tasks to run. One goal of the PR is fix an issue where rebuild jobs which failed on develop pipelines did not properly report the broken full hash to the "broken-specs-url". |
||
|---|---|---|
| .. | ||
| bash | ||
| csh | ||
| docker | ||
| docs/docker/module-file-tutorial | ||
| gitlab | ||
| keys | ||
| logo | ||
| qa | ||
| templates | ||
| setup-env.csh | ||
| setup-env.fish | ||
| setup-env.sh | ||
| setup-tutorial-env.sh | ||
| spack-completion.bash | ||