Commit 397552b2 authored by Marcel Amirault's avatar Marcel Amirault

Merge branch 'docs-jobs-version-rem' into 'master'

Remove outdated GitLab version refs from Jobs

See merge request gitlab-org/gitlab!71487
parents 9a931232 d0e56b43
...@@ -45,8 +45,6 @@ Clicking an individual job shows you its job log, and allows you to: ...@@ -45,8 +45,6 @@ Clicking an individual job shows you its job log, and allows you to:
## See why a job failed ## See why a job failed
> [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 When a pipeline fails or is allowed to fail, there are several places where you
can find the reason: can find the reason:
...@@ -58,8 +56,7 @@ In each place, if you hover over the failed job you can see the reason it failed ...@@ -58,8 +56,7 @@ In each place, if you hover over the failed job you can see the reason it failed
![Pipeline detail](img/job_failure_reason.png) ![Pipeline detail](img/job_failure_reason.png)
In [GitLab 10.8 and later](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/17814), You can also see the reason it failed on the Job detail page.
you can also see the reason it failed on the Job detail page.
## The order of jobs in a pipeline ## The order of jobs in a pipeline
...@@ -87,8 +84,6 @@ For example: ...@@ -87,8 +84,6 @@ For example:
## Group jobs in a pipeline ## Group jobs in a pipeline
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/6242) in GitLab 8.12.
If you have many similar jobs, your [pipeline graph](../pipelines/index.md#visualize-pipelines) becomes long and hard If you have many similar jobs, your [pipeline graph](../pipelines/index.md#visualize-pipelines) becomes long and hard
to read. to read.
...@@ -164,8 +159,6 @@ for a single run of the manual job. ...@@ -164,8 +159,6 @@ for a single run of the manual job.
## Delay a job ## Delay a job
> [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`](../jobs/job_control.md#run-a-job-after-a-delay) keyword to When you do not want to run a job immediately, you can use the [`when:delayed`](../jobs/job_control.md#run-a-job-after-a-delay) keyword to
delay a job's execution for a certain period. delay a job's execution for a certain period.
......
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