Skip to content

G
gitlab-ce
Commit f710c1d1 authored by Matija Čupić's avatar Matija Čupić
Browse files
Options

Document multi-project variable precedence

parent ab509c78
Hide whitespace changes
Inline Side-by-side
Showing with 5 additions and 0 deletions
doc/ci/multi_project_pipelines.md
View file @ f710c1d1
...@@ -171,6 +171,11 @@ In this scenario, the `UPSTREAM_BRANCH` variable with a value related to the ...@@ -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 upstream pipeline will be passed to the `downstream-job` job, and will be available
within the context of all downstream builds. 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 ### Limitations
Because bridge jobs are a little different to regular jobs, it is not Because bridge jobs are a little different to regular jobs, it is not
......
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
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7