Commit 6726348b authored by Evan Read's avatar Evan Read

Merge branch 'poffey21-master-patch-97817' into 'master'

Document that CI stages can be invisible

See merge request gitlab-org/gitlab!61821
parents dc7476a0 2c0bb9d8
...@@ -152,6 +152,13 @@ are the default pipeline stages. ...@@ -152,6 +152,13 @@ are the default pipeline stages.
If a job does not specify a [`stage`](#stage), the job is assigned the `test` stage. If a job does not specify a [`stage`](#stage), the job is assigned the `test` stage.
If a stage is defined, but no jobs use it, the stage is not visible in the pipeline. This is
useful for [compliance pipeline configuration](../../user/project/settings/index.md#compliance-pipeline-configuration)
because:
- Stages can be defined in the compliance configuration but remain hidden if not used.
- The defined stages become visible when developers use them in job definitions.
To make a job start earlier and ignore the stage order, use To make a job start earlier and ignore the stage order, use
the [`needs`](#needs) keyword. the [`needs`](#needs) keyword.
......
...@@ -77,7 +77,9 @@ The user running the pipeline in the project should at least have Reporter acces ...@@ -77,7 +77,9 @@ The user running the pipeline in the project should at least have Reporter acces
Example `.compliance-gitlab-ci.yml` Example `.compliance-gitlab-ci.yml`
```yaml ```yaml
stages: # Allows compliance team to control the ordering and interweaving of stages/jobs # Allows compliance team to control the ordering and interweaving of stages/jobs.
# Stages without jobs defined will remain hidden.
stages:
- pre-compliance - pre-compliance
- build - build
- test - test
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment