From 110b76de52719b3b7a697528039f53082ae8d8de Mon Sep 17 00:00:00 2001 From: Achilleas Pipinellis Date: Wed, 17 Apr 2019 09:10:10 +0000 Subject: [PATCH] Merge branch 'docs/merge-request-pipelines' into 'master' Add note about MR Pipeline Runner version Closes gitlab-ee#11122 See merge request gitlab-org/gitlab-ce!27330 (cherry picked from commit 2c5398ee96799440523a03c7c770e90a9629762a) f5155180 Add note about MR Pipeline Runner version --- doc/ci/merge_request_pipelines/index.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) 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. -- GitLab