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
c4938045
Commit
c4938045
authored
Jul 27, 2017
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Explain all possible values of 'only' and 'except'
parent
842bcfa7
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
17 additions
and
4 deletions
+17
-4
doc/ci/yaml/README.md
doc/ci/yaml/README.md
+17
-4
No files found.
doc/ci/yaml/README.md
View file @
c4938045
...
...
@@ -441,13 +441,25 @@ There are a few rules that apply to the usage of refs policy:
*
`only`
and
`except`
are inclusive. If both
`only`
and
`except`
are defined
in a job specification, the ref is filtered by
`only`
and
`except`
.
*
`only`
and
`except`
allow the use of regular expressions.
*
`only`
and
`except`
allow the use of special keywords:
`api`
,
`branches`
,
`external`
,
`tags`
,
`pushes`
,
`schedules`
,
`triggers`
, and
`web`
*
`only`
and
`except`
allow to specify a repository path to filter jobs for
forks.
In addition,
`only`
and
`except`
allow the use of special keywords:
|
**Value**
|
**Description**
|
| --------- | ---------------- |
|
`branches`
| When a branch is pushed. |
|
`tags`
| When a tag is pushed. |
|
`api`
| When pipeline has been triggered by a second pipelines API (not triggers API). |
|
`external`
| When using CI services other than GitLab. |
|
`pipelines`
| For multi-project triggers, created using the API with
`CI_JOB_TOKEN`
. |
|
`pushes`
| Pipeline is triggered by a
`git push`
by the user. |
|
`schedules`
| For
[
scheduled pipelines
][
schedules
]
. |
|
`triggers`
| For pipelines created using a trigger token. |
|
`web`
| For pipelines created using
**Run pipeline**
button in GitLab UI (under your project's
**Pipelines**
). |
In the example below,
`job`
will run only for refs that start with
`issue-`
,
whereas all branches will be skipped
.
whereas all branches will be skipped
:
```
yaml
job
:
...
...
@@ -460,7 +472,7 @@ job:
```
In this example,
`job`
will run only for refs that are tagged, or if a build is
explicitly requested via an API trigger or a
[
Pipeline Schedule
]
(
../../user/project/pipelines/schedules.md
)
.
explicitly requested via an API trigger or a
[
Pipeline Schedule
]
[
schedules
]
:
```
yaml
job
:
...
...
@@ -1532,3 +1544,4 @@ CI with various languages.
[
ce-7983
]:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7983
[
ce-7447
]:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7447
[
ce-3442
]:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3442
[
schedules
]:
../../user/project/pipelines/schedules.md
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