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
6dc060f3
Commit
6dc060f3
authored
May 09, 2020
by
Thiago Figueiró
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add except example to troubleshooting section
See
https://gitlab.com/groups/gitlab-org/-/epics/2300
for details
parent
d33ad2c0
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
25 additions
and
0 deletions
+25
-0
doc/user/application_security/index.md
doc/user/application_security/index.md
+25
-0
No files found.
doc/user/application_security/index.md
View file @
6dc060f3
...
...
@@ -394,6 +394,31 @@ spotbugs-sast:
-
if
:
$CI_MERGE_REQUEST_ID
```
If your override is aimed at limiting jobs to only run on branches, not tags,
it would look similar to:
```
yaml
include
:
-
template
:
SAST.gitlab-ci.yml
# Ensure that the scanning is not executed on tags
spotbugs-sast
:
except
:
-
tags
```
To transition to the new
`rules`
syntax, the override would be rewritten as:
```
yaml
include
:
-
template
:
SAST.gitlab-ci.yml
# Ensure that the scanning is not executed on tags
spotbugs-sast
:
rules
:
-
if
:
$CI_COMMIT_TAG ==
null
```
[
Learn more on the usage of `rules`
](
../../ci/yaml/README.md#rules
)
.
#### Pin your templates to the deprecated versions
...
...
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