Show an error in the pipeline simulation when pipeline will not run due to all jobs being filtered out by rules
Problem to solve
In 12.8, we made a change so that pipelines with only .pre
and/or .post
stages would not run.
This leads to pipelines not being started without any error message or warning. This has caused trouble for some of our customers that only have .pre
or .post
jobs. To make things more confusing, the Yaml linter shows it as valid Yaml (which it is).
This problem occurs not only with .pre or .post jobs but also in any scenario when all jobs are filtered out by config rules.
Proposal
Make it possible to use the pipeline simulation in the pipeline editor to check whether a pipeline will not run for the selected trigger due to all jobs being filtered out.
Update the simulation to show an error when pipeline can't be created for the selected trigger due to no jobs being added.
Documentation
What does success look like, and how can we measure that?
Some indication of why the pipeline did not start is shown.
Links / references
Customer ticket: https://gitlab.zendesk.com/agent/tickets/158333 (internal use)