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
aa0b0dc2
Commit
aa0b0dc2
authored
Mar 25, 2020
by
Seth Berger
Committed by
Achilleas Pipinellis
Mar 25, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update secure integration document
parent
6ea0c852
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
6 deletions
+4
-6
doc/development/integrations/secure.md
doc/development/integrations/secure.md
+4
-6
No files found.
doc/development/integrations/secure.md
View file @
aa0b0dc2
...
...
@@ -70,7 +70,7 @@ mysec_dependency_scanning:
`gl-sast-report.json`
is an example file path. See
[
the Output file section
](
#output-file
)
for more details.
It is processed as a SAST report because it is declared as such in the job definition.
###
Rul
es
###
Polici
es
Scanning jobs should be skipped unless the corresponding feature is listed
in the
`GITLAB_FEATURES`
variable (comma-separated list of values).
...
...
@@ -103,11 +103,9 @@ mysec_dependency_scanning:
$CI_PROJECT_REPOSITORY_LANGUAGES =~ /\bjava\b/
```
The
[
`only/except`
](
../../ci/yaml/README.md#onlyexcept-basic
)
keywords
as well as the new
[
`rules`
](
../../ci/yaml/README.md#rules
)
keyword
make possible to trigger the job depending on the branch, or when some particular file changes.
Such rules should be defined by users based on their needs,
and should not be predefined in the job definition of the scanner.
Any additional job policy should only be configured by users based on their needs.
For instance, predefined policies should not trigger the scanning job
for a particular branch or when a particular set of files changes.
## Docker image
...
...
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