diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-08-31 12:13:01 +0000 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-08-31 12:13:01 +0000 |
commit | 3034c7e6aa99d21c3d9fa1df01f60fdd3f32d914 (patch) | |
tree | 424f5a291abf1a93ff9870667ecb301b899972fc /doc/development/integrations | |
parent | 6170bdc060501ecf6f817a530b3dc9f2e39ad4c3 (diff) | |
download | gitlab-ce-3034c7e6aa99d21c3d9fa1df01f60fdd3f32d914.tar.gz |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/integrations')
-rw-r--r-- | doc/development/integrations/secure.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/integrations/secure.md b/doc/development/integrations/secure.md index 741fa8d89c4..0227dc9147c 100644 --- a/doc/development/integrations/secure.md +++ b/doc/development/integrations/secure.md @@ -254,7 +254,7 @@ Following the POSIX exit code standard, the scanner exits with 0 for success and Success also includes the case when vulnerabilities are found. When a CI job fails, security report results are not ingested by GitLab, even if the job -[allows failure](../../ci/yaml/#allow_failure). The report artifacts are still uploaded to GitLab and available +[allows failure](../../ci/yaml/index.md#allow_failure). The report artifacts are still uploaded to GitLab and available for [download in the pipeline security tab](../../user/application_security/vulnerability_report/pipeline.md#download-security-scan-outputs). When executing a scanning job using the [Docker-in-Docker privileged mode](../../user/application_security/sast/index.md#requirements), |