Add syntax for importing a job that is "virtual" so it is not run by default
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
For our specific use-case of utilizing container scanning, we want to create multiple scanning jobs in a single pipeline.
gitlab-com/gl-infra/k8s-workloads/gitlab-com!43 (merged)
To accomplish this, we imported the Container-Scanning.gitlab-ci.yml template and created three jobs that extend container_scanning, each of them change some of the parameters on the job.
We do not however, want to run the base container_scanning job, it would be a bit cleaner if we had specific syntax to indicate that the job is virtual, and shouldn't be run. To work around this, we simply added an except condition that prevented the base job from running.
@tmaczukin suggested in a conversation in slack that we might consider introducing new syntax for this to make it explicit:
container_scanning:
virtual: true