diff options
| author | Winnie Hellmann <winnie@gitlab.com> | 2018-10-11 02:50:42 +0000 |
|---|---|---|
| committer | Evan Read <eread@gitlab.com> | 2018-10-11 02:50:42 +0000 |
| commit | cd42e9ad3a90756a4d2b28ec921b1ceb57579d4f (patch) | |
| tree | 340f63cc8b287f5f1fed78ca3636dc3704686209 /doc/ci/pipelines.md | |
| parent | f810ff639a8253c27a4c34e14c665eed96be654c (diff) | |
| download | gitlab-ce-cd42e9ad3a90756a4d2b28ec921b1ceb57579d4f.tar.gz | |
Documentation for delayed jobs
Diffstat (limited to 'doc/ci/pipelines.md')
| -rw-r--r-- | doc/ci/pipelines.md | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/ci/pipelines.md b/doc/ci/pipelines.md index ea47d676edb..44589500eb0 100644 --- a/doc/ci/pipelines.md +++ b/doc/ci/pipelines.md @@ -193,6 +193,18 @@ stage has a job with a manual action.  +### Delay a particular job in the pipeline graph + +> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/21767) in GitLab 11.4. + +When you do not want to run a job immediately, you can [delay the job to run after a certain period](yaml/README.md#delayed). +This is especially useful for timed incremental rollout that new code is rolled out gradually. +For example, if you start rolling out new code and users do not experience trouble, GitLab automatically completes the deployment from 0% to 100%. +Alternatively, if you start rolling out and you noticed that a few users experience trouble with the version, +you can stop the timed incremental rollout by canceling the pipeline, and [rolling](environments.md#rolling-back-changes) it back to the stable version. + + + ### Ordering of jobs in pipeline graphs **Regular pipeline graph** @@ -211,6 +223,7 @@ by name. The order of severity is: - pending - running - manual +- scheduled - canceled - success - skipped |