Remove depSASTer triggered pipeline
What does this MR do and why?
DepSASTer Removal (gitlab-com/gl-security/product-security&10 - closed) revealed that, at present, depSASTer is not delivering value and instead adds almost entirely unhelpful noise.
This MR removes depSASTer from the gitlab-org/gitlab
pipeline.
-
Identify where depSASTer is referenced: https://gitlab.com/search?search=depsaster&nav_source=navbar&project_id=278964&group_id=9970&search_code=true&repository_ref=master -
Remove the trigger pipeline job from .gitlab/ci/static-analysis.gitlab-ci.yml
-
Remove its boolean in .gitlab-ci.yml
-
Remove the rules from .gitlab/ci/rules.gitlab-ci.yml
-
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.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Related to #460792 (closed)
Edited by Nick Malcolm