Don't run Auto DevOps when no dockerfile or matching buildpack exists
Problem to solve
Currently we run auto devops automatically even for projects that:
- Don't have a dockerfile
- Don't have a matching buildpack
This leads to unnecessary cycles and user dissatisfaction as they often don't understand why their project is showing failures.
Sasha, Software Developer, https://design.gitlab.com/research/personas#persona-sasha
Devon, DevOps Engineer, https://design.gitlab.com/research/personas#persona-devon
When Auto DevOps is enabled, evaluate if a build mechanism exists before running. If not build mechanism, disable Auto DevOps.
Considering introducing a new "evaluating" pipeline type which always passes. Based on its result we leave enabled or disable with matching user notification.
What does success look like, and how can we measure that?
We should track the instances where this evaluation returned true or false to start.