diff options
| author | Itzik Gan Baruch <iganbarouch@gitlab.com> | 2019-06-04 15:53:14 +0000 |
|---|---|---|
| committer | Itzik Gan Baruch <iganbarouch@gitlab.com> | 2019-06-04 15:53:14 +0000 |
| commit | 59914a856be4e8b19da7a8a848183a572e563af2 (patch) | |
| tree | f16fa1bd19a18c506b38a93f992c1ae79018467f | |
| parent | b2a560a7c75ce28fd068b70296c9d0fafdace7cf (diff) | |
| download | gitlab-ce-59914a856be4e8b19da7a8a848183a572e563af2.tar.gz | |
Added a link to the click-through demoiganbaruch-master-patch-15162
| -rw-r--r-- | doc/ci/multi_project_pipelines.md | 4 |
1 files changed, 4 insertions, 0 deletions
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 |