diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-09-05 18:09:58 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-09-05 18:09:58 +0300 |
| commit | d298c12de58b4d0a28358d38ed3f5762ed1550a0 (patch) | |
| tree | cceec04d4312aadd4ef315fe851ff3cab4faca77 /doc/ci/resource_groups/index.md | |
| parent | e67e43e958982189b5ba3b816744ab162a34dd4b (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/resource_groups/index.md')
| -rw-r--r-- | doc/ci/resource_groups/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ci/resource_groups/index.md b/doc/ci/resource_groups/index.md index c215ef412a1..dff52a742a8 100644 --- a/doc/ci/resource_groups/index.md +++ b/doc/ci/resource_groups/index.md @@ -210,7 +210,7 @@ Read more how you can use GitLab for [safe deployments](../environments/deployme Because [`oldest_first` process mode](#process-modes) enforces the jobs to be executed in a pipeline order, there is a case that it doesn't work well with the other CI features. -For example, when you run [a child pipeline](../pipelines/parent_child_pipelines.md) +For example, when you run [a child pipeline](../pipelines/downstream_pipelines.md#parent-child-pipelines) that requires the same resource group with the parent pipeline, a dead lock could happen. Here is an example of a _bad_ setup: |