Don't run Auto DevOps for projects which don't have a runner configured
Problem to solve
Currently, Auto DevOps runs jobs even when no runner is configured for the project. This causes the jobs to hang indefinitely providing no real value to end users.
For example, projects that are either A) sample projects never meant to be run on CI or B) projects not meant to built on GitLab CI (but another CI system instead) will both run and show hanging pipelines.
Proposal
Extend Auto DevOps logic which decides whether or not to run a pipeline to include the presence of a runner.
-
Do not run (or auto enable) Auto DevOps for projects that do not have a shared runner configured.
-
If user tries to manually enable Auto DevOps, present clear messaging of what's required for Auto DevOps.
-
Will still run for explicitly enabled auto devops, regardless of runner configuration
What does success look like, and how can we measure that?
(If no way to measure success, link to an issue that will implement a way to measure this)