diff options
Diffstat (limited to 'doc/ci/pipelines.md')
| -rw-r--r-- | doc/ci/pipelines.md | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/doc/ci/pipelines.md b/doc/ci/pipelines.md index 71c4c9ca0ec..161160f7218 100644 --- a/doc/ci/pipelines.md +++ b/doc/ci/pipelines.md @@ -43,7 +43,7 @@ As an example, imagine a pipeline consisting of four stages, executed in the fol ## Visualizing pipelines -> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/5742) in GitLab 8.11. +> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/5742) in GitLab 8.11. Pipelines can be complex structures with many sequential and parallel jobs. @@ -87,7 +87,7 @@ Stages in pipeline mini graphs are collapsible. Hover your mouse over them and c Job ordering depends on the type of pipeline graph. For [regular pipeline graphs](#regular-pipeline-graphs), jobs are sorted by name. -For [pipeline mini graphs](#pipeline-mini-graphs) ([introduced](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/9760) +For [pipeline mini graphs](#pipeline-mini-graphs) ([introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/9760) in GitLab 9.0), jobs are sorted by severity and then by name. The order of severity is: @@ -180,7 +180,7 @@ through the GitLab UI: ### Grouping jobs -> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/6242) in GitLab 8.12. +> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/6242) in GitLab 8.12. If you have many similar jobs, your [pipeline graph](#visualizing-pipelines) becomes long and hard to read. @@ -333,7 +333,7 @@ Clicking on an individual job will show you its job log, and allow you to: ### Seeing the failure reason for jobs -> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/17782) in GitLab 10.7. +> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/17782) in GitLab 10.7. When a pipeline fails or is allowed to fail, there are several places where you can quickly check the reason it failed: @@ -346,12 +346,12 @@ In each place, if you hover over the failed job you can see the reason it failed  -From [GitLab 10.8](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/17814), +From [GitLab 10.8](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/17814), you can also see the reason it failed on the Job detail page. ### Manual actions from pipeline graphs -> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/7931) in GitLab 8.15. +> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/7931) in GitLab 8.15. Manual actions, configured using the [`when:manual`](yaml/README.md#whenmanual) parameter, allow you to require manual interaction before moving forward in the pipeline. @@ -367,7 +367,7 @@ stage has a job with a manual action. ### Specifying variables when running manual jobs -> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/30485) in GitLab 12.2. +> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/30485) in GitLab 12.2. When running manual jobs you can supply additional job specific variables. @@ -381,7 +381,7 @@ environment variables. ### Delay a job in a pipeline graph -> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/21767) in GitLab 11.4. +> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/21767) in GitLab 11.4. When you do not want to run a job immediately, you can use the [`when:delayed`](yaml/README.md#whendelayed) parameter to delay a job's execution for a certain period. @@ -408,7 +408,7 @@ GitLab provides API endpoints to: ### Start multiple manual actions in a stage -> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/27188) in GitLab 11.11. +> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/27188) in GitLab 11.11. Multiple manual actions in a single stage can be started at the same time using the "Play all manual" button. Once the user clicks this button, each individual manual action will be triggered and refreshed @@ -466,7 +466,7 @@ runners will not use regular runners, they must be tagged accordingly. ## Persistent pipeline refs -> [Introduced](https://gitlab.com/gitlab-org/gitlab/merge_requests/17043) in GitLab 12.4. +> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/17043) in GitLab 12.4. Previously, you'd have encountered unexpected pipeline failures when you force-pushed a branch to its remote repository. To illustrate the problem, suppose you've had the current workflow: |