[Feature flag] Enable `jira_connect_create_branch`
Summary
This issue is to rollout the feature "Create branch from Jira Issue" on production,
that is currently behind the jira_connect_create_branch
feature flag. Feature issue is #2647 (closed).
Owners
- Team: ~"group::ecosystem" Category:Integrations
- Most appropriate slack channel to reach out to:
#g_create_ecosystem
- Best individual to reach out to: @tomquirk / @toupeira
- PM: @mushakov
Stakeholders
The Rollout Plan
- Partial Rollout on GitLab.com with testing groups
- Rollout on GitLab.com for a certain period (How long)
- Percentage Rollout on GitLab.com
- Rollout Feature for everyone as soon as it's ready
Testing Groups/Projects/Users
-
gitlab-org/gitlab
project -
gitlab-org
/gitlab-com
groups - ...
Expectations
What are we expecting to happen?
What might happen if this goes wrong?
What can we monitor to detect problems with this?
Rollout Steps
Rollout on non-production environments
-
Ensure that the feature MRs have been deployed to non-production environments. -
/chatops run auto_deploy status <merge-commit-of-your-feature>
-
-
Enable the feature globally on non-production environments. -
/chatops run feature set <feature-flag-name> true --dev
-
/chatops run feature set <feature-flag-name> true --staging
-
-
Verify that the feature works as expected. Posting the QA result in this issue is preferable.
Preparation before production rollout
-
Ensure that the feature MRs have been deployed to both production and canary. -
/chatops run auto_deploy status <merge-commit-of-your-feature>
-
-
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.[ ] If the feature might impact the user experience, notify#support_gitlab-com
and your team channel (more guidance when this is necessary in the dev docs).-
If the feature flag in code has an actor, enable it on GitLab.com for testing groups/projects.-
/chatops run feature set --<actor-type>=<actor> <feature-flag-name> true
-
-
Verify that the feature works as expected. Posting the QA result in this issue is preferable.
Global rollout on production
We'll be removing the feature flag immediately, and skipping to the next section.
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. !67471 (merged)-
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 <feature-flag-name> --dev
-
/chatops run feature delete <feature-flag-name> --staging
-
/chatops run feature delete <feature-flag-name>
-
-
Close this rollout issue.
Edited by Tom Quirk