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
6177fdbe
Commit
6177fdbe
authored
Apr 08, 2020
by
Can Eldem
Committed by
Nick Gaskill
Apr 08, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Tell SAST, DS detection is based on default branch (non-DinD)
parent
c2db4e3e
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
9 additions
and
2 deletions
+9
-2
doc/user/application_security/dependency_scanning/index.md
doc/user/application_security/dependency_scanning/index.md
+5
-1
doc/user/application_security/sast/index.md
doc/user/application_security/sast/index.md
+4
-1
No files found.
doc/user/application_security/dependency_scanning/index.md
View file @
6177fdbe
...
...
@@ -204,7 +204,11 @@ to start relevant analyzers depending on the detected repository language(s) ins
are some differences in the way repository languages are detected between DIND and non-DIND. You can
observe these differences by checking both Linguist and the common library. For instance, Linguist
looks for
`*.java`
files to spin up the
[
gemnasium-maven
](
https://gitlab.com/gitlab-org/security-products/analyzers/gemnasium-maven
)
image, while orchestrator only looks for the existence of
`pom.xml`
or
`build.gradle`
.
image, while orchestrator only looks for the existence of
`pom.xml`
or
`build.gradle`
. GitLab uses
Linguist to detect new file types in the default branch. This means that when introducing files or
dependencies for a new language or package manager, the corresponding scans won't be triggered in
the MR and will only run on the default branch once the MR is merged. This will be addressed by
[
#211702
](
https://gitlab.com/gitlab-org/gitlab/-/issues/211702
)
.
## Interacting with the vulnerabilities
...
...
doc/user/application_security/sast/index.md
View file @
6177fdbe
...
...
@@ -193,7 +193,10 @@ are some differences in the way repository languages are detected between DIND a
observe these differences by checking both Linguist and the common library. For instance, Linguist
looks for
`*.java`
files to spin up the
[
spotbugs
](
https://gitlab.com/gitlab-org/security-products/analyzers/spotbugs
)
image, while orchestrator only looks for the existence of
`pom.xml`
,
`build.xml`
,
`gradlew`
,
`grailsw`
, or
`mvnw`
.
`grailsw`
, or
`mvnw`
. GitLab uses Linguist to detect new file types in the default branch. This
means that when introducing files or dependencies for a new language or package manager, the
corresponding scans won't be triggered in the MR and will only run on the default branch once the
MR is merged. This will be addressed by
[
#211702
](
https://gitlab.com/gitlab-org/gitlab/-/issues/211702
)
.
#### Enabling kubesec analyzer
...
...
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