Merge branch 'docs/edit-click-through' into 'master'
Integrate demo link into content more See merge request gitlab-org/gitlab-ce!29242
This commit is contained in:
commit
a80c6a68b5
1 changed files with 4 additions and 4 deletions
|
@ -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
|
||||
|
|
Loading…
Reference in a new issue