diff options
Diffstat (limited to 'doc/ci/pipelines/pipeline_architectures.md')
| -rw-r--r-- | doc/ci/pipelines/pipeline_architectures.md | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/ci/pipelines/pipeline_architectures.md b/doc/ci/pipelines/pipeline_architectures.md index e36eb24055f..1e4d32fc331 100644 --- a/doc/ci/pipelines/pipeline_architectures.md +++ b/doc/ci/pipelines/pipeline_architectures.md @@ -23,13 +23,18 @@ own advantages. These methods can be mixed and matched if needed: - [Multi-project pipelines](downstream_pipelines.md#multi-project-pipelines): Good for larger products that require cross-project interdependencies, like those with a [microservices architecture](https://about.gitlab.com/blog/2016/08/16/trends-in-version-control-land-microservices/). + For example, you might deploy your web application from three different GitLab projects. + With multi-project pipelines you can trigger a pipeline in each project, where each + has its own build, test, and deploy process. You can visualize the connected pipelines + in one place, including all cross-project interdependencies. + <i class="fa fa-youtube-play youtube" aria-hidden="true"></i> For an overview, see the [Multi-project pipelines demo](https://www.youtube.com/watch?v=g_PIwBM1J84). ## Basic Pipelines This is the simplest pipeline in GitLab. It runs everything in the build stage concurrently, -and once all of those finish, it runs everything in the test stage the same way, and so on. +and once all of those finish, it runs everything in the test and subsequent stages the same way. It's not the most efficient, and if you have lots of steps it can grow quite complex, but it's easier to maintain: |