You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+26-5Lines changed: 26 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Procedure:
27
27
2. Convert report
28
28
3. Upload converted report as junit report
29
29
30
-
**Example for Secret Scanning**
30
+
### Example for Secret Scanning
31
31
This example can be used as is.
32
32
```yaml
33
33
stages:
@@ -55,7 +55,7 @@ secret_convert:
55
55
junit: gl-secret-detection-report.xml
56
56
```
57
57
58
-
**Example for SAST**
58
+
### Example for SAST
59
59
Since GitLab decides dynamically which scanners to use depending on project languages, it makes sense to first perform a testrun only including the template. This way one can see which jobs are executed and then overwrite them.
60
60
```yaml
61
61
stages:
@@ -105,9 +105,9 @@ brakeman-sast-convert:
105
105
106
106
```
107
107
108
-
**Example for Container Scanning**
108
+
### Example for Container Scanning
109
109
110
-
```yml
110
+
```yaml
111
111
- include:
112
112
- template: Jobs/Build.gitlab-ci.yml #Build and push the container image
113
113
- template: Security/Container-Scanning.gitlab-ci.yml #Scan the built image
@@ -130,7 +130,7 @@ container_scanning-convert:
130
130
junit: gl-container-scanning-report.xml
131
131
```
132
132
133
-
**Suppression**
133
+
### Suppression
134
134
135
135
You can provide a file with suppression which will allow to ignore some vulnerabilities.
136
136
@@ -151,6 +151,27 @@ And now you can modify execution commands as follows:
0 commit comments