Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Boxiang Sun
gitlab-ce
Commits
f5155180
Commit
f5155180
authored
Apr 12, 2019
by
Steve Azzopardi
Committed by
Steve Azzopardi
Apr 17, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add note about MR Pipeline Runner version
parent
44be329d
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
1 deletion
+7
-1
doc/ci/merge_request_pipelines/index.md
doc/ci/merge_request_pipelines/index.md
+7
-1
No files found.
doc/ci/merge_request_pipelines/index.md
View file @
f5155180
# Pipelines for merge requests
# 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.
> [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
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:
...
@@ -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
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,
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
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
(then running a pipeline on that ref), we can better test that the combined result
is also valid.
is also valid.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment