Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
GitLab
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Analytics
Analytics
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Commits
Open sidebar
projects.thm.de
GitLab
Commits
ba1b2ab9
Commit
ba1b2ab9
authored
Feb 11, 2019
by
Jason Lenny
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Apply suggestion to doc/ci/merge_request_pipelines/index.md
parent
98569488
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
doc/ci/merge_request_pipelines/index.md
doc/ci/merge_request_pipelines/index.md
+1
-1
No files found.
doc/ci/merge_request_pipelines/index.md
View file @
ba1b2ab9
...
...
@@ -62,7 +62,7 @@ The behavior of the `only: merge_requests` rule is such that _only_ jobs with
that rule are run in the context of a merge request; no other jobs will be run.
However, you may what to reverse this behaviour, having all of your jobs to run _except_
for one or two. Consider the following pipeline, with jobs
A B and C
. If you want
for one or two. Consider the following pipeline, with jobs
`A`
,
`B`
, and
`C`
. If you want
all pipelines to always run
`A`
and
`B`
, but only want
`C`
to run for a merge request,
you can configure your
`.gitlab-ci.yml`
file as follows:
...
...
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