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
d34498d0
Commit
d34498d0
authored
May 28, 2019
by
GitLab Bot
Browse files
Options
Browse Files
Download
Plain Diff
Automatic merge of gitlab-org/gitlab-ce master
parents
d65fc412
9daae83f
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
23 additions
and
6 deletions
+23
-6
doc/ci/yaml/README.md
doc/ci/yaml/README.md
+23
-6
No files found.
doc/ci/yaml/README.md
View file @
d34498d0
...
...
@@ -386,17 +386,12 @@ job:
-
branches@gitlab-org/gitlab-ce
except
:
-
master@gitlab-org/gitlab-ce
-
release/.*
@gitlab-org/gitlab-ce
-
/^release/.*$/
@gitlab-org/gitlab-ce
```
The above example will run
`job`
for all branches on
`gitlab-org/gitlab-ce`
,
except
`master`
and those with names prefixed with
`release/`
.
NOTE:
**Note:**
Because
`@`
is used to denote the beginning of a ref's repository path,
matching a ref name containing the
`@`
character in a regular expression
requires the use of the hex character code match
`\x40`
.
If a job does not have an
`only`
rule,
`only: ['branches', 'tags']`
is set by
default. If it doesn't have an
`except`
rule, it is empty.
...
...
@@ -415,6 +410,28 @@ job:
only
:
[
'
branches'
,
'
tags'
]
```
#### Regular expressions
Because
`@`
is used to denote the beginning of a ref's repository path,
matching a ref name containing the
`@`
character in a regular expression
requires the use of the hex character code match
`\x40`
.
Only the tag or branch name can be matched by a regular expression.
The repository path, if given, is always matched literally.
If a regular expression shall be used to match the tag or branch name,
the entire ref name part of the pattern has to be a regular expression,
and must be surrounded by
`/`
.
(With regular expression flags appended after the closing
`/`
.)
So
`issue-/.*/`
won't work to match all tag names or branch names
that begin with
`issue-`
.
TIP:
**Tip**
Use anchors
`^`
and
`$`
to avoid the regular expression
matching only a substring of the tag name or branch name.
For example,
`/^issue-.*$/`
is equivalent to
`/^issue-/`
,
while just
`/issue/`
would also match a branch called
`severe-issues`
.
### Supported `only`/`except` regexp syntax
CAUTION:
**Warning:**
...
...
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