Automatically disable Auto DevOps for project upon first pipeline failure
When Auto DevOps is on by default at instance level, projects run pipelines automatically. This is good, but there could be projects that are not compatible with Auto DevOps template, and so pipelines will fail. Having pipelines running all the time for those projects is a waste of resources, and we should prevent it from happening.
If a project has Auto DevOps enabled because of instance default to
on, and the first Auto DevOps pipelines failed, the Auto DevOps setting should be automatically turned off for that project.
Users should receive an email, so they can be aware of what Auto DevOps tried to do, improve the code and enable it again (see https://gitlab.com/gitlab-org/gitlab-ce/issues/45284).
If the first pipeline succeeds, or Auto DevOps is explicitly enabled for the project, no auto-off will happen.
The email should be only sent to the project owner and the user who triggered the pipeline
The Auto DevOps pipeline failed for pipeline #19 and has been disabled for minimal-ruby-app-test.
In order to use the Auto DevOps pipeline with your project, please review the currently supported languages,
adjust your project accordingly, and turn on the Auto DevOps pipeline within your CI/CD project settings.
currently supported languages-> https://docs.gitlab.com/ee/topics/autodevops/#currently-supported-languages
Learn more about Auto DevOps-> https://docs.gitlab.com/ee/topics/autodevops/
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.