diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-10-24 09:07:07 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-10-24 09:07:07 +0300 |
commit | 12287a65b735d784cda3555d1b261e50b461b29e (patch) | |
tree | e7539b1b3672986a4f41b544f913ee120d623d44 /doc/ci/multi_project_pipelines.md | |
parent | 24ed154fa81265f47bcfbecfcb331f82a5faad0d (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/multi_project_pipelines.md')
-rw-r--r-- | doc/ci/multi_project_pipelines.md | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/ci/multi_project_pipelines.md b/doc/ci/multi_project_pipelines.md index 093d334e937..f13d05716f1 100644 --- a/doc/ci/multi_project_pipelines.md +++ b/doc/ci/multi_project_pipelines.md @@ -87,10 +87,9 @@ not be found, or a user does not have access rights to create pipeline there, the `staging` job is going to be marked as _failed_. CAUTION: **Caution:** -`staging` will succeed as soon as a downstream pipeline gets created. -GitLab does not support status attribution yet, however adding first-class -`trigger` configuration syntax is ground work for implementing -[status attribution](https://gitlab.com/gitlab-org/gitlab-foss/issues/39640). +In the example, `staging` will be marked as succeeded as soon as a downstream pipeline +gets created. If you want to display the downstream pipeline's status instead, see +[Mirroring status from triggered pipeline](#mirroring-status-from-triggered-pipeline). NOTE: **Note:** Bridge jobs do not support every configuration entry that a user can use |