summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEvan Read <eread@gitlab.com>2019-07-31 00:31:40 +0000
committerEvan Read <eread@gitlab.com>2019-07-31 00:31:40 +0000
commitb54234498aab810f178f7875db2ad636f507f3e4 (patch)
treec3c9e8505d6cd4a05b8671433dd63066301552a4
parentbdff11850732028b9f7a2b2f5bb8f5fa5991b427 (diff)
parentf710c1d1c77db3c27156f45e6c81dc06d304d32c (diff)
downloadgitlab-ce-b54234498aab810f178f7875db2ad636f507f3e4.tar.gz
Merge branch 'mc/doc/variable-precedence-docs' into 'master'
Document multi-project variable precedence Closes gitlab-ee#12879 See merge request gitlab-org/gitlab-ce!31291
-rw-r--r--doc/ci/multi_project_pipelines.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/ci/multi_project_pipelines.md b/doc/ci/multi_project_pipelines.md
index 463b9194c58..ced4344a0b0 100644
--- a/doc/ci/multi_project_pipelines.md
+++ b/doc/ci/multi_project_pipelines.md
@@ -171,6 +171,11 @@ In this scenario, the `UPSTREAM_BRANCH` variable with a value related to the
upstream pipeline will be passed to the `downstream-job` job, and will be available
within the context of all downstream builds.
+NOTE: **Tip:**
+Upstream pipelines take precedence over downstream ones. If there are two
+variables with the same name defined in both upstream and downstream projects,
+the ones defined in the upstream project will take precedence.
+
### Limitations
Because bridge jobs are a little different to regular jobs, it is not