Backend: Provide troubleshooting information for jobs that do not run
Problem to solve
There is a common situation where a customer may attempt to use a CI job, such as our Security jobs, but see the failure "No jobs in pipeline". This is largely due to the templates having specific pre-conditions; i.e. only.variables: $GITLAB_FEATURES =~ /\bsast\b/
, that prevent the jobs from executing without an appropriate license.
Intended users
Update 2022-12-16
The current error message for when no jobs can be run due to the rules configuration is No stages / jobs for this pipeline.
Proposal
Improve debugging instructions and/or error message when this occurs.
The proposed message is:
Pipeline will not run for the selected trigger. The rules configuration prevented any jobs from being added to the pipeline.
Permissions and Security
No change to permissions
Documentation
Improve debugging documentation for the case when no jobs run but a pipeline is considered valid.
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Implementation
backend | MR |
---|---|
Update CI error message when pipeline has no jobs to run | !107297 (merged) |
Edited by Leaminn Ma