[new_pipelines_table] Roll out plan
What
This feature flag is a refactor of the pipelines table. We are moving the table to utilize GlTable
.
Where? CI/CD > Pipelines
Rollout and test the :new_pipelines_table
feature flag.
Remove the :new_pipelines_table
feature flag in a timely manner once deemed stable.
Owners
- Team: ~"group::continuous integration"
- Most appropriate slack channel to reach out to:
#s_verify_fe
or#g_ci
- Best individual to reach out to: @pburdette
Expectations
What are we expecting to happen?
Smooth refactor where no visual bugs happen and all functionality stays the same.
What might happen if this goes wrong?
There could be visual bugs from using GlTable
or certain actions might not be the same. In this case we rollback and fix.
What can we monitor to detect problems with this?
The responsible engineer will monitor the projects enabled for the first phase of the rollout, before enabling fully.
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.
-
gitlab-org/gitlab-ui
project -
gitlab-org/gitlab
project
Roll Out Steps
-
Enable on staging ( /chatops run feature set feature_name 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 --project=gitlab-org/gitlab feature_name 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 feature_name 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 -
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 new_pipelines_table false