Dependency Scanning custom images support
Following #5232 (closed), and similar to #5773 (closed), we could let the users use their own, custom docker images for Dependency Scanning. For example, some users have issues with the current Dependency Scanning image, as it requires
docker:dind to work correctly. Therefore, they are running directly the new Java Maven image, by naming the job
While this is working fine, it's limiting the options to only one job (Java Maven in this case).
This issue is to allow users to create
dependency_scanning:<custom job name> jobs.
- The job name is a convention, and must start with
- The job must create an artifact named
Specify the format for
- Update backend to aggregate all artifacts in one report (this is transparent for FrontEnd).