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
The above example will create a `dast` job in your CI pipeline and will allow
26
-
you to download and analyze the report artifact in JSON format.
28
+
The above example will create a `dast` job in your CI/CD pipeline which will run
29
+
the tests on the URL defined in the `website` variable (change it to use your
30
+
own) and finally write the results in the `gl-dast-report.json` file. You can
31
+
then download and analyze the report artifact in JSON format.
27
32
28
33
TIP: **Tip:**
29
34
Starting with [GitLab Enterprise Edition Ultimate][ee] 10.4, this information will
30
35
be automatically extracted and shown right in the merge request widget. To do
31
36
so, the CI job must be named `dast` and the artifact path must be
32
37
`gl-dast-report.json`.
33
-
[Learn more on dynamic application security testing results shown in merge requests](https://docs.gitlab.com/ee/user/project/merge_requests/dast.html).
38
+
[Learn more about DAST results shown in merge requests](https://docs.gitlab.com/ee/user/project/merge_requests/dast.html).
0 commit comments