Skip to content

Not possibly to explicitly disable Auto DevOps on a project?

Summary

There seems to be no documentation -- and perhaps no feature? -- for disabling Auto DevOps, or CI/CD generally, on a project.

Steps to reproduce

  • Receive an email about Auto DevOps (because Auto DevOps is now being enabled by default)
  • Try to explicitly disable it on this project
  • Try to explicitly disable it on other projects, before they have Auto DevOps auto-enabled

Example Project

I saw this on private projects on gitlab.com

What is the expected correct behavior?

There's a project state to actively disable (i.e. explicitly disable, as opposed to simply not enabling) either Auto DevOps, or all CI/CD in general. (Though I'd prefer an explicit UI, if needed the UI could be identical to the current UI, setting the "explicitly disabled" flag if the user ever changes the existing "Auto DevOps" check box from checked to unchecked at https://gitlab.com///settings/ci_cd . Perhaps that's the case already and just not documented?)

If it is explicitly disabled, it is not auto-enabled on that project later on.

There is documentation on https://docs.gitlab.com/ee/topics/autodevops/ saying how Auto DevOps can be explicitly disabled: https://docs.gitlab.com/ee/topics/autodevops/

What is the current bug behavior?

As far as I can tell, there are no docs saying how to disable it, nor perhaps even a feature to explicitly disable it at all?

Not finding any feature like this, I did my best to disable it by adding an invalid .gitlab-ci.yml to every repository. Ironically I think this causes some small amount of code to run for every commit, sending me spam email for every commit I push -- but it does appear to have the effect I intended of not running the bulk of the Auto DevOps code on my repositories. I understand that Auto DevOps would be disabled after first failing run, but I prefer to not run it the first time either if possible.

Results of GitLab environment info

Expand for output related to GitLab environment info 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)
Edited by John Lee