diff options
| author | Steve Azzopardi <steveazz@outlook.com> | 2019-04-12 20:09:13 +0200 |
|---|---|---|
| committer | Steve Azzopardi <sazzopardi@gitlab.com> | 2019-04-17 08:53:13 +0200 |
| commit | f5155180aad9162982caf5090523e08d85e29f8f (patch) | |
| tree | 29a5cb234dc185cf28f009a24748186a384943cb | |
| parent | 44be329d59bc20598c2c2f310d4f3029c8dd25a9 (diff) | |
| download | gitlab-ce-docs/merge-request-pipelines.tar.gz | |
Add note about MR Pipeline Runner versiondocs/merge-request-pipelines
| -rw-r--r-- | doc/ci/merge_request_pipelines/index.md | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/doc/ci/merge_request_pipelines/index.md b/doc/ci/merge_request_pipelines/index.md index 4f61e97bd8a..2de751c9e62 100644 --- a/doc/ci/merge_request_pipelines/index.md +++ b/doc/ci/merge_request_pipelines/index.md @@ -1,5 +1,11 @@ # Pipelines for merge requests +NOTE: **Note**: +As of GitLab 11.10, pipelines for merge requests require GitLab Runner 11.9 +or higher due to the [recent refspecs +changes](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/25504). +Anything lower will cause the pipeline to fail. + > [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/15310) in GitLab 11.6. Usually, when you create a new merge request, a pipeline runs with the @@ -68,7 +74,7 @@ when a merge request was created or updated. For example: It's possible for your source and target branches to diverge, which can result in the scenario that source branch's pipeline was green, the target's pipeline was green, but the combined output fails. By having your merge request pipeline automatically -create a new ref that contains the merge result of the source and target branch +create a new ref that contains the merge result of the source and target branch (then running a pipeline on that ref), we can better test that the combined result is also valid. |