diff options
| author | Matija Čupić <matteeyah@gmail.com> | 2019-07-30 17:10:29 +0300 |
|---|---|---|
| committer | Matija Čupić <matteeyah@gmail.com> | 2019-07-31 03:25:51 +0300 |
| commit | f710c1d1c77db3c27156f45e6c81dc06d304d32c (patch) | |
| tree | 24c2a78d5da722a129019bdbe2d23b9e1550f587 | |
| parent | ab509c78929d9b5f4e02d013e8911ac9d0a07aad (diff) | |
Document multi-project variable precedence
| -rw-r--r-- | doc/ci/multi_project_pipelines.md | 5 |
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 |