diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-09 06:07:59 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-09 06:07:59 +0300 |
commit | ce130e211808c9b02116f30af4a043f1a4d3a717 (patch) | |
tree | 133b0cb229d979361518e806189223eb99edf6c3 /doc/ci/multi_project_pipelines.md | |
parent | ed4df05ce917d6cf175aeb508b0485ae5f281a0a (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/multi_project_pipelines.md')
-rw-r--r-- | doc/ci/multi_project_pipelines.md | 44 |
1 files changed, 28 insertions, 16 deletions
diff --git a/doc/ci/multi_project_pipelines.md b/doc/ci/multi_project_pipelines.md index e41a6f0d9b1..d56935dc3a3 100644 --- a/doc/ci/multi_project_pipelines.md +++ b/doc/ci/multi_project_pipelines.md @@ -2,26 +2,18 @@ type: reference --- -# Multi-project pipelines **(PREMIUM)** +# Multi-project pipelines -> [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/2121) in -[GitLab Premium 9.3](https://about.gitlab.com/releases/2017/06/22/gitlab-9-3-released/#multi-project-pipeline-graphs). +> - [Introduced](https://about.gitlab.com/releases/2015/08/22/gitlab-7-14-released/#build-triggers-api-gitlab-ci) in GitLab 7.14, as Build Triggers. +> - [Made available](https://gitlab.com/gitlab-org/gitlab/issues/199224) in all tiers in GitLab 12.8. -When you set up [GitLab CI/CD](README.md) across multiple projects, you can visualize -the entire pipeline, including all cross-project inter-dependencies. +You can set up [GitLab CI/CD](README.md) across multiple projects, so that a pipeline +in one project can trigger a pipeline in another project. ## Overview -GitLab CI/CD is a powerful continuous integration tool that works not only per project, but also across projects. When you -configure GitLab CI for your project, you can visualize the stages -of your [jobs](pipelines.md#configuring-pipelines) on a [pipeline graph](pipelines.md#visualizing-pipelines). - -![Multi-project pipeline graph](img/multi_project_pipeline_graph.png) - -In the Merge Request Widget, multi-project pipeline mini-graphs are displayed, -and when hovering or tapping (on touchscreen devices) they will expand and be shown adjacent to each other. - -![Multi-project mini graph](img/multi_pipeline_mini_graph.gif) +GitLab CI/CD is a powerful continuous integration tool that works not only per project, +but also across projects with multi-project pipelines. 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/blog/2016/08/16/trends-in-version-control-land-microservices/). @@ -30,6 +22,9 @@ For a demonstration of how cross-functional development teams can use cross-pipe 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). +Additionally, it's possible to visualize the entire pipeline, including all cross-project +inter-dependencies. **(PREMIUM)** + ## Use cases Let's assume you deploy your web app from different projects in GitLab: @@ -40,8 +35,25 @@ Let's assume you deploy your web app from different projects in GitLab: With Multi-Project Pipelines you can visualize the entire pipeline, including all build and test stages for the three projects. +## Multi-project pipeline visualization **(PREMIUM)** + +> [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/2121) in [GitLab Premium 9.3](https://about.gitlab.com/releases/2017/06/22/gitlab-9-3-released/#multi-project-pipeline-graphs). + +When you configure GitLab CI for your project, you can visualize the stages of your +[jobs](pipelines.md#configuring-pipelines) on a [pipeline graph](pipelines.md#visualizing-pipelines). + +![Multi-project pipeline graph](img/multi_project_pipeline_graph.png) + +In the Merge Request Widget, multi-project pipeline mini-graphs are displayed, +and when hovering or tapping (on touchscreen devices) they will expand and be shown adjacent to each other. + +![Multi-project mini graph](img/multi_pipeline_mini_graph.gif) + ## Triggering multi-project pipelines through API +> - Use of `CI_JOB_TOKEN` for multi-project pipelines was [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/2017) in [GitLab Premium][ee] 9.3. +> - Use of `CI_JOB_TOKEN` for multi-project pipelines was [made available](https://gitlab.com/gitlab-org/gitlab/issues/31573) in all tiers in GitLab 12.4. + When you use the [`CI_JOB_TOKEN` to trigger pipelines](triggers/README.md#ci-job-token), GitLab recognizes the source of the job token, and thus internally ties these pipelines together, allowing you to visualize their relationships on pipeline graphs. @@ -52,7 +64,7 @@ outbound connections for upstream and downstream pipeline dependencies. ## Creating multi-project pipelines from `.gitlab-ci.yml` > - [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/8997) in [GitLab Premium](https://about.gitlab.com/pricing/) 11.8. -> - [Moved](https://gitlab.com/gitlab-org/gitlab/issues/199224) to GitLab Core in 12.8. +> - [Made available](https://gitlab.com/gitlab-org/gitlab/issues/199224) in all tiers in 12.8. ### Triggering a downstream pipeline using a bridge job |