summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEvan Read <eread@gitlab.com>2019-06-03 10:25:18 +1000
committerEvan Read <eread@gitlab.com>2019-06-03 10:26:31 +1000
commit707e87c64bbf9c979088f612ba28bd99c29d1085 (patch)
tree1db59eda408ff7f1f502d03fdde44a6260e0eb92
parent763d911245e99d4b7df43dcf16e0dc0e0fe2bf13 (diff)
downloadgitlab-ce-docs/edit-downstream-variables.tar.gz
Further review comments addeddocs/edit-downstream-variables
-rw-r--r--doc/ci/multi_project_pipelines.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/ci/multi_project_pipelines.md b/doc/ci/multi_project_pipelines.md
index 67a009f26da..40638d151c4 100644
--- a/doc/ci/multi_project_pipelines.md
+++ b/doc/ci/multi_project_pipelines.md
@@ -139,8 +139,8 @@ 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 to the downstream pipeline
-that is created when the `trigger-downstream` job is queued. This is because downstream pipelines
-inherit variables declared in global `variables` blocks.
+that is created when the `trigger-downstream` job is queued. This is because `trigger-downstream`
+job inherits variables declared in global variables blocks, and then we pass these variables to a downstream pipeline.
```yaml
variables: