From 59914a856be4e8b19da7a8a848183a572e563af2 Mon Sep 17 00:00:00 2001 From: Itzik Gan Baruch Date: Tue, 4 Jun 2019 15:53:14 +0000 Subject: Added a link to the click-through demo --- doc/ci/multi_project_pipelines.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'doc/ci') diff --git a/doc/ci/multi_project_pipelines.md b/doc/ci/multi_project_pipelines.md index bcd92243d97..57825982ede 100644 --- a/doc/ci/multi_project_pipelines.md +++ b/doc/ci/multi_project_pipelines.md @@ -166,6 +166,10 @@ 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. +### 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 -- cgit v1.2.3