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
1
Merge Requests
1
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
nexedi
gitlab-ce
Commits
bcc97a32
Commit
bcc97a32
authored
May 26, 2020
by
Melvin Vermeeren
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: cicd: yaml: clarify rules:if when behaviour
parent
dde42885
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
13 additions
and
4 deletions
+13
-4
changelogs/unreleased/33040-doc-cicd-yaml-clarify-rules-if-when-behaviour.yml
...d/33040-doc-cicd-yaml-clarify-rules-if-when-behaviour.yml
+5
-0
doc/ci/yaml/README.md
doc/ci/yaml/README.md
+8
-4
No files found.
changelogs/unreleased/33040-doc-cicd-yaml-clarify-rules-if-when-behaviour.yml
0 → 100644
View file @
bcc97a32
---
doc
:
"
cicd:
yaml:
clarify
rules:if
when
behaviour"
merge_request
:
33040
author
:
Melvin Vermeeren
type
:
changed
doc/ci/yaml/README.md
View file @
bcc97a32
...
@@ -1014,10 +1014,14 @@ job:
...
@@ -1014,10 +1014,14 @@ job:
-
if
:
'
$CI_MERGE_REQUEST_SOURCE_BRANCH_NAME'
# If neither of the first two match but the simple presence does, we set to "on_success" by default
-
if
:
'
$CI_MERGE_REQUEST_SOURCE_BRANCH_NAME'
# If neither of the first two match but the simple presence does, we set to "on_success" by default
```
```
If none of the provided rules match, the job will be set to
`when:never`
, and
Some details regarding the logic that determines the
`when`
for the job:
not included in the pipeline. If
`rules:when`
is not included in the configuration
at all, the behavior defaults to
`job:when`
, which continues to default to
-
If none of the provided rules match, the job is set to
`when: never`
, and is
`on_success`
.
not included in the pipeline.
-
A rule without any conditional clause, such as a
`when`
or
`allow_failure`
rule without
`if`
or
`changes`
, always matches, and is always used if reached.
-
If a rule matches and has no
`when`
defined, the rule will use the
`when`
defined for the job, which defaults to
`on_success`
if not defined.
#### `rules:changes`
#### `rules:changes`
...
...
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