Feature flag rollout - scoped_group_variables
What
Remove the :scoped_group_variables
feature flag ...
Owners
- Team: Configure
- Most appropriate slack channel to reach out to:
#s_configure
- Best individual to reach out to: @tigerwnz
Expectations
What are we expecting to happen?
- Extra UI elements will be shown in group level CI variable settings, allowing environment scopes to be configured for variables.
- Group level CI variables that are configured with the above UI will only be selected by jobs that deploy to the specified environment.
What might happen if this goes wrong?
- Group CI variable form does not submit properly
- Variables are not chosen for the correct CI job
- CI jobs fail to start
What can we monitor to detect problems with this?
- Grafana: POST /api/jobs/request
- Grafana:
Groups::Settings::CiCdController#show
- Grafana:
Groups::VariablesController#update
Beta groups/projects
If applicable, any groups/projects that are happy to have this feature turned on early. Some organizations may wish to test big changes they are interested in with a small subset of users ahead of time for example.
Roll Out Steps
-
Enable on staging ( /chatops run feature set scoped_group_variables true --staging
) -
Test on staging - [-] Ensure that documentation has been updated
-
Enable on GitLab.com for individual groups/projects listed above and verify behaviour ( /chatops run feature set --group=gitlab-org/contribute-workshops scoped_group_variables true
) -
Coordinate a time to enable the flag with the SRE oncall and release managers - In
#production
mention@sre-oncall
and@release-managers
. Once an SRE on call and Release Manager on call confirm, you can proceed with the rollout
- In
-
Announce on the issue an estimated time this will be enabled on GitLab.com -
Enable on GitLab.com by running chatops command in #production
(/chatops run feature set scoped_group_variables true
) -
Cross post chatops Slack command to #support_gitlab-com
(more guidance when this is necessary in the dev docs) and in your team channel -
Announce on the issue that the flag has been enabled -
Remove feature flag and add changelog entry. Ensure that the feature flag definition YAML file has been removed in the same MR that is removing the feature flag from the code - !58200 (merged) -
After the flag removal is deployed, clean up the feature flag by running chatops command in #production
channel
Rollback Steps
-
This feature can be disabled by running the following Chatops command:
/chatops run feature set scoped_group_variables false
Edited by Tiger Watson