From 707e87c64bbf9c979088f612ba28bd99c29d1085 Mon Sep 17 00:00:00 2001 From: Evan Read Date: Mon, 3 Jun 2019 10:25:18 +1000 Subject: Further review comments added --- doc/ci/multi_project_pipelines.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc') 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: -- cgit v1.2.1