Add SAST_EXCLUDED_PATHS option
What does this MR do?
Add SAST_EXCLUDED_PATHS
option to filter vulnerabilities on affected file (upgrade to common@v2.3.0)
This depends on gitlab-org/security-products/analyzers/common!34 (merged)
TODO
-
Revert to tagged version of common
once gitlab-org/security-products/analyzers/common!34 (merged) is merged
What are the relevant issue numbers?
https://gitlab.com/gitlab-org/gitlab-ee/issues/10030
Does this MR meet the acceptance criteria?
-
Changelog entry added - [-] Documentation created/updated for GitLab EE, if necessary
-
Documentation created/updated for this project, if necessary - [-] Documentation reviewed by technical writer or follow-up review issue created
-
Tests added for this feature/bug -
Job definition updated, see https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/12081 & https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28018 -
Job definition example - [-] CI Templates (to be removed)
-
Vendored CI Templates in EE (also in CE) -
Ensure that all of the ENV vars supported are propagated to Docker containers upon docker run
in job definitions
-
-
Conforms to the code review guidelines -
Conforms to the Go guidelines - [-] Security reports checked/validated by reviewer
Edited by Fabien Catteau