diff options
| author | Evan Read <eread@gitlab.com> | 2019-06-06 11:53:01 +1000 |
|---|---|---|
| committer | Evan Read <eread@gitlab.com> | 2019-06-07 10:36:05 +1000 |
| commit | 83537216b50ec41043eb96810fc0cfc3cb646b37 (patch) | |
| tree | f5010f701a2827657395088748b07d7b5d3e908d | |
| parent | 76a69e06f0342b5132ebc4d66578a580ab3e00e2 (diff) | |
| download | gitlab-ce-docs/edit-click-through.tar.gz | |
Integrate demo link into content moredocs/edit-click-through
| -rw-r--r-- | doc/ci/multi_project_pipelines.md | 8 |
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 |