summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAchilleas Pipinellis <axil@gitlab.com>2019-06-07 07:57:19 +0000
committerAchilleas Pipinellis <axil@gitlab.com>2019-06-07 07:57:19 +0000
commita80c6a68b542a33808315e7c2871cd48c1245391 (patch)
tree514a449e9e380a5401ae4129ab5611b7a5121a25
parentc0dc00876b4054ec15fe42217a39cc412100c047 (diff)
parent41ae0014f00afe012ab4a1b59ed29829685cec37 (diff)
downloadgitlab-ce-a80c6a68b542a33808315e7c2871cd48c1245391.tar.gz
Merge branch 'docs/edit-click-through' into 'master'
Integrate demo link into content more See merge request gitlab-org/gitlab-ce!29242
-rw-r--r--doc/ci/multi_project_pipelines.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/ci/multi_project_pipelines.md b/doc/ci/multi_project_pipelines.md
index 1091129a9dc..50c8d82602b 100644
--- a/doc/ci/multi_project_pipelines.md
+++ b/doc/ci/multi_project_pipelines.md
@@ -26,6 +26,10 @@ and when hovering or tapping (on touchscreen devices) they will expand and be sh
Multi-project pipelines are useful for larger products that require cross-project inter-dependencies, such as those
adopting a [microservices architecture](https://about.gitlab.com/2016/08/16/trends-in-version-control-land-microservices/).
+For a demonstration of how cross-functional development teams can use cross-pipeline
+triggering to trigger multiple pipelines for different microservices projects, see
+[Cross-project Pipeline Triggering and Visualization](https://about.gitlab.com/handbook/marketing/product-marketing/demo/#cross-project-pipeline-triggering-and-visualization-may-2019---1110).
+
## Use cases
Let's assume you deploy your web app from different projects in GitLab:
@@ -167,10 +171,6 @@ 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.
-### Demos
-
-[A click-through demo of cross-project pipeline is available](https://about.gitlab.com/handbook/marketing/product-marketing/demo/#cross-project-pipeline-triggering-and-visualization-may-2019---1110), demonstrates how cross-functional dev teams use cross-pipeline triggering to trigger multiple pipelines for different microservices projects.
-
### Limitations
Because bridge jobs are a little different to regular jobs, it is not