Use original order of analyzers for DS_DEFAULT_ANALYZERS value
What does this MR do?
When updating the job template for Dependency Scanning
in order to get rid of Docker-in-Docker,
CI variable DS_DEFAULT_ANALYZERS
has been set to a value
that doesn't match the defaults set in depenency-scanning,
resulting in a change in the generated reports.
This bug affects developers working on Dependency Scanning but should have NO significant impact on users.
This have no consequence when Docker-in-Docker is disabled, which will eventually become the default.
Old value in dependency-scanning CI config:
DS_DEFAULT_ANALYZERS: bundler-audit,retire.js,gemnasium,gemnasium-maven,gemnasium-python
New value in dependency scanning job template:
DS_DEFAULT_ANALYZERS: "gemnasium, retire.js, gemnasium-python, gemnasium-maven, bundler-audit"`
This MR reverts that change and put original order of DS_DEFAULT_ANALYZERS
Related issue #36738 (closed)
Does this MR meet the acceptance criteria?
Dependency scanning QA test projects should not fail
Conformity
Edited by 🤖 GitLab Bot 🤖