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

Merge branch 'docs/gb/expand-downstream-pipeline-variables' into 'master' 

Docs for a downstream pipeline variables expansion

See merge request gitlab-org/gitlab-ce!28828
This commit is contained in:
Douglas Barbosa Alexandre 2019-05-28 17:08:05 +00:00
parent 1215a3f1ad d9f871f1d6
commit 7f97c5a802
1 changed files with 28 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
doc/ci/multi_project_pipelines.md
View File

@ -134,6 +134,34 @@ staging:
The `ENVIRONMENT` variable will be passed to every job defined in a downstream
pipeline. It will be available as an environment variable when GitLab Runner picks a job.
In the following configuration, the `MY_VARIABLE` variable will be passed
downstream, because jobs inherit variables declared in top-level `variables`:
```yaml
variables:
MY_VARIABLE: my-value
my-pipeline:
variables:
ENVIRONMENT: something
trigger: my/project
```
You might want to pass some information about the upstream pipeline using, for
example, predefined variables. In order to do that, you can use interpolation
to pass any variable. For example:
```yaml
my-pipeline:
variables:
UPSTREAM_BRANCH: $CI_COMMIT_REF_NAME
trigger: my/project
```
In this scenario, the `UPSTREAM_BRANCH` variable with a value related to the
upstream pipeline will be passed to a `downstream` job, and will be available
within the context of all downstream builds.
### Limitations
Because bridge jobs are a little different to regular jobs, it is not