Add no-op for removed Dependency Scanning jobs
Description
Add the two jobs removed in 15.0 back as dummy jobs, since users may have overridden these and rely on the removed job names.
The override is to simple add a message in the script
section with the note about removal.
The two jobs' rules are set to when: never
so that the job doesn't trigger for the included template.
Scenarios
Currently, for any user customized either one of the two jobs (bundler-audit-dependency_scanning
, retire-js-dependency_scanning
), they are getting a ci linting error with the job undefined.
Here are the scenarios that we are looking at handling (examples below are for bundler-audit-dependency_scanning
):
scenario | what happens now | what happens after this MR |
---|---|---|
1. user didn't customize the job | nothing | nothing |
2. user customized the job rules | ci lint error | job fails with warning message (pipeline passes (see allow_failure )) - example
|
3. user customized the job script section | ci lint error | job doesn't run b/c of the when: never run rule - example
|
4. user customized the job variables, image name, etc. | ci lint error | job doesn't run (when: never ) - example
|
5. user customized the job's rules and script section | ci lint error | job runs as customized - example |
Related issues
Edited by Igor Frenkel