Remove Dependency Scanning artifact from CS template
What does this MR do and why?
The Container Scanning CI job no longer generates a Dependency Scanning report so we can remove the corresponding artifact report configuration from the CS job definition in the CI template.
see Remove Dependency Scanning report generation fr... (#439782 - closed)
This change is not a breaking change. The file generation has already been removed from the analyzer executed within this job. Currently the attempt to upload the artifact is failing but without harming the execution or downstream processes. This MR simply cleans things up.
If a customer has overridden the CI job's artifact definition in their CI config, this change won't impact them.
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.