Skip to content

Remove DEBUG from CS for registry job

Aditya Tiwari requested to merge remove-debug-from-cs into master

What does this MR do and why?

As part of GitLab Container Registry: Continuous Vulnerabi... (&2340 - closed), we have introduced a trigger CS job that runs on every container registry image push with the latest tag. Previously, there was a requirement for DEBUG logging because of ongoing development, but it is no longer necessary and can be removed to minimize unnecessary output.

CS_DISABLE_DEPENDENCY_LIST is deprecated hence removing it too. https://docs.gitlab.com/ee/user/application_security/container_scanning/#available-cicd-variables

Remove DEBUG from scan service Remove DEBUG log from ScanImageService CS job Changelog: added EE: true

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Numbered steps to set up and validate the change are strongly suggested.

  1. Run the feature using instructions here https://docs.gitlab.com/ee/user/application_security/continuous_vulnerability_scanning/#continuous-vulnerability-scanning-for-container-registry

  2. Check that DEBUG log does not show up.

Edited by Aditya Tiwari

Merge request reports