Rollout ci_pending_builds_async_update feature flag
Summary
This issue is to rollout ci pending build asynchronous update on production,
that is currently behind the ci_pending_builds_async_update
feature flag.
Owners
- Team: grouppipeline execution
- Most appropriate slack channel to reach out to:
#g_pipeline-execution
- Best individual to reach out to: @morefice
- PM: ?
Stakeholders
Expectations
What are we expecting to happen?
When a project or group is transferred a new worker is kicked off to keep Ci::PendingBuild
in sync.
What might happen if this goes wrong?
If a project or group is transferred in Canary because we don't have Sidekiq, the jobs would be stuck for a while.
What can we monitor to detect problems with this?
What can we check for monitoring production after rollouts?
Consider adding links to check for Sentry errors, Production logs for 5xx, 302s, etc.
Rollout Steps
Rollout on non-production environments
- Ensure that the feature MRs have been deployed to non-production environments.
-
/chatops run auto_deploy status 574144e1f3b7f3e5c54b344f8259c2046f3b0cda
-
-
Enable the feature globally on non-production environments. -
/chatops run feature set ci_pending_builds_async_update true --dev
-
/chatops run feature set ci_pending_builds_async_update true --staging
-
-
Verify that the feature works as expected. Posting the QA result in this issue is preferable.
Specific rollout on production
- Ensure that the feature MRs have been deployed to both production and canary.
-
/chatops run auto_deploy status 574144e1f3b7f3e5c54b344f8259c2046f3b0cda
-
- If you're using project-actor, you must enable the feature on these entries:
-
/chatops run feature set ci_pending_builds_async_update 10
-
-
Verify that the feature works on the specific entries. Posting the QA result in this issue is preferable.
Preparation before global rollout
-
Check if the feature flag change needs to be accompanied with a change management issue. Cross link the issue here if it does. -
Ensure that you or a representative in development can be available for at least 2 hours after feature flag updates in production. If a different developer will be covering, or an exception is needed, please inform the oncall SRE by using the @sre-oncall
Slack alias. -
Ensure that documentation has been updated (More info). -
Announce on the feature issue an estimated time this will be enabled on GitLab.com. -
Notify #support_gitlab-com
and your team channel (more guidance when this is necessary in the dev docs).
Global rollout on production
For visibility, all /chatops
commands that target production should be executed in the #production
slack channel and cross-posted (with the command results) to the responsible team's slack channel (#g_TEAM_NAME
).
-
Incrementally roll out the feature. - If the feature flag in code does NOT have an actor, perform time-based rollout (random rollout).
-
/chatops run feature set ci_pending_builds_async_update 10
-
/chatops run feature set ci_pending_builds_async_update 25
-
/chatops run feature set ci_pending_builds_async_update 50
-
- Enable the feature globally on production environment.
-
/chatops run feature set ci_pending_builds_async_update true
-
- If the feature flag in code does NOT have an actor, perform time-based rollout (random rollout).
-
Announce on the feature issue that the feature has been globally enabled. -
Wait for at least one day for the verification term.
Release the feature
After the feature has been deemed stable, the clean up should be done as soon as possible to permanently enable the feature and reduce complexity in the codebase.
-
Create a merge request to remove <feature-flag-name>
feature flag. Ask for review and merge it.-
Remove all references to the feature flag from the codebase. -
Remove the YAML definitions for the feature from the repository. -
Create a changelog entry.
-
-
Ensure that the cleanup MR has been deployed to both production and canary. If the merge request was deployed before the code cutoff, the feature can be officially announced in a release blog post. -
/chatops run auto_deploy status <merge-commit-of-cleanup-mr>
-
-
Close the feature issue to indicate the feature will be released in the current milestone. -
Clean up the feature flag from all environments by running these chatops command in #production
channel:-
/chatops run feature delete ci_pending_builds_async_update --dev
-
/chatops run feature delete ci_pending_builds_async_update--staging
-
/chatops run feature delete ci_pending_builds_async_update
-
-
Close this rollout issue.
Rollback Steps
-
This feature can be disabled by running the following Chatops command:
/chatops run feature set ci_pending_builds_async_update false