diff options
Diffstat (limited to 'doc/ci/pipelines.md')
| -rw-r--r-- | doc/ci/pipelines.md | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/doc/ci/pipelines.md b/doc/ci/pipelines.md index eaa6efc526d..de9bac76281 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-ce/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-ce/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: @@ -146,7 +146,7 @@ The union of A, B, and C is (1, 4) and (6, 7). Therefore, the total running time ### Expanding and collapsing job log sections -> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/14664) in GitLab +> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/14664) in GitLab > 12.0. Job logs are divided into sections that can be collapsed or expanded. @@ -179,7 +179,7 @@ through the GitLab UI: ### Grouping jobs -> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/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. @@ -204,7 +204,7 @@ the following (you can even use them interchangeably): - A colon (`:`). NOTE: **Note:** -More specifically, it uses [this](https://gitlab.com/gitlab-org/gitlab-ce/blob/2f3dc314f42dbd79813e6251792853bc231e69dd/app/models/commit_status.rb#L99) regular expression: `\d+[\s:\/\\]+\d+\s*`. +More specifically, it uses [this](https://gitlab.com/gitlab-org/gitlab-foss/blob/2f3dc314f42dbd79813e6251792853bc231e69dd/app/models/commit_status.rb#L99) regular expression: `\d+[\s:\/\\]+\d+\s*`. #### How grouping works @@ -291,7 +291,7 @@ Clicking on an individual job will show you its job trace, and allow you to: ### Seeing the failure reason for jobs -> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/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: @@ -304,12 +304,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-ce/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-ce/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. @@ -325,7 +325,7 @@ stage has a job with a manual action. ### Specifying variables when running manual jobs -> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/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. @@ -339,7 +339,7 @@ environment variables. ### Delay a job in a pipeline graph -> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/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. @@ -366,7 +366,7 @@ GitLab provides API endpoints to: ### Start multiple manual actions in a stage -> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/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 |