kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Document multi-project variable precedence

Browse source
This commit is contained in:
Matija Čupić 2019-07-30 16:10:29 +02:00
parent ab509c7892
commit f710c1d1c7
No known key found for this signature in database
GPG key ID: 4BAF84FFACD2E5DE
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
doc/ci/multi_project_pipelines.md
View file

@ -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