Skip to content
GitLab
Next
Closed
Issue created by Taurie Davis@tauriedavisDeveloper

Enable/disable Auto DevOps at the Group level

Problem to solve

Currently, gitlab.com users with multiple projects have to iterate through all projects in order to disable auto devops. Furthermore, as we rollout our staggered enablement of the feature some users may get some of their projects enabled and not others.

Further details

(Include use cases, benefits, and/or goals)

Proposal

Provide a mechanism through which users can disable auto devops for the gitlab.com top level group. Furthermore, if the setting is set to disable, our staggered rollout should ignore the group and not enable.

Solution

An owner first visiting their group settings will find that the Auto DevOps pipeline is enabled for all projects within their group:

Screen_Shot_2019-01-17_at_9.31.00_AM

Owners will be able to turn off the setting, removing the instance enabled badge and disabling the Auto DevOps pipeline on all projects that haven't been explicitly set.

Group with Auto DevOps setting off, instance enabled removed

Screen_Shot_2019-01-17_at_9.34.31_AM

Project that was enabled via the instance level is no longer enabled

Screen_Shot_2019-01-17_at_9.35.52_AM

If a user turns off the instance enablement at a group level and then turns it back on, the badge under projects should read group enabled

Screen_Shot_2019-01-17_at_9.39.20_AM

If a user turns off the group enablement at a project level, then the badge should be removed.

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)

Links / references

Re: https://gitlab.slack.com/archives/CB07X8AQ3/p1539092581000100

Edited by Daniel Gruesso