Enable zip_pages_deployments feature flag
What
-
Remove the :deploy_pages_as_zip
feature flag introduced in #228782 (closed) -
Remove rescue in create_pages_deployment
method
Owners
- Team: ~"group::release management"
#gitlab-pages
- Best individual to reach out to: @vshushlin
Expectations
What are we expecting to happen?
New PagesDeployment
models gets created per new pages deployment
What might happen if this goes wrong?
New pages deployments can break
What can we monitor to detect problems with this?
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
project -
gitlab-org
/gitlab-com
groups - ...
Roll Out Steps
-
Enable on staging -
Test on staging -
Ensure that documentation has been updated -
Enable on GitLab.com for individual groups/projects listed above and verify behaviour -
Coordinate a time to enable the flag with #production
and#g_delivery
on slack. -
Announce on the issue an estimated time this will be enabled on GitLab.com -
Enable on GitLab.com by running chatops command in #production
-
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 -
After the flag removal is deployed, clean up the feature flag by running chatops command in #production
channel