diff options
| author | Evan Read <eread@gitlab.com> | 2019-06-06 01:46:56 +0000 |
|---|---|---|
| committer | Evan Read <eread@gitlab.com> | 2019-06-06 01:46:56 +0000 |
| commit | bf6eb21e110896d5c0bdc7a51f9a5467e315365d (patch) | |
| tree | 88e33179b14919bfa19ca924d68e11eb982242ea | |
| parent | 58328ca9dc7828cbbf4b36a4f782f1b8dc3e8fb8 (diff) | |
| parent | 59914a856be4e8b19da7a8a848183a572e563af2 (diff) | |
| download | gitlab-ce-bf6eb21e110896d5c0bdc7a51f9a5467e315365d.tar.gz | |
Merge branch 'iganbaruch-master-patch-15162' into 'master'
Added a link to the click-through demo
See merge request gitlab-org/gitlab-ce!29148
| -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 40638d151c4..1091129a9dc 100644 --- a/doc/ci/multi_project_pipelines.md +++ b/doc/ci/multi_project_pipelines.md @@ -167,6 +167,10 @@ 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 |