diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-01-22 06:09:04 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-01-22 06:09:04 +0300 |
| commit | 6ef43e2aa1cad78daaed93eff1aebd6a4e7e18a6 (patch) | |
| tree | b0f41c623936fd3b187aa302403d9bba10369b41 /doc/development/integrations | |
| parent | 21796f414cf380088217c1a76a4c3ba5d7b6fdd1 (diff) | |
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, 2 insertions, 0 deletions
diff --git a/doc/development/integrations/secure.md b/doc/development/integrations/secure.md index fb9d894d203..1d5aced5869 100644 --- a/doc/development/integrations/secure.md +++ b/doc/development/integrations/secure.md @@ -260,6 +260,8 @@ When executing command lines, scanners should use the `debug` level to log the c For instance, the [bundler-audit](https://gitlab.com/gitlab-org/security-products/analyzers/bundler-audit) scanner uses the `debug` level to log the command line `bundle audit check --quiet`, and what `bundle audit` writes to the standard output. +If the command line fails, then it should be logged with the `error` log level; +this makes it possible to debug the problem without having to change the log level to `debug` and rerun the scanning job. #### common logutil package |