[Feature flag] Rollout ci_retry_downstream_pipeline
[Feature flag] Enable ci_retry_downstream_pipeline
Summary
NOTE: This feature got cancelled, so the rollout was also cancelled.
This issue is to rollout the feature on production,
that is currently behind the ci_retry_downstream_pipeline
feature flag.
Owners
- Team: grouppipeline authoring
- Most appropriate slack channel to reach out to:
#g_pipeline_authoring
- Best individual to reach out to: @mgandres (frontend) @lauraX (backend)
- PM: @dhershkovitch
Rollout Steps
Rollout on non-production environments
-
Ensure that the feature MRs have been deployed to non-production environments. -
/chatops run auto_deploy status 83b9fdb72395f37da360ff7ed1a3906ad20a8db0
-
-
Enable the feature globally on non-production environments. -
/chatops run feature set ci_retry_downstream_pipeline true --dev
-
/chatops run feature set ci_retry_downstream_pipeline 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 83b9fdb72395f37da360ff7ed1a3906ad20a8db0
-
- If you're using project-actor, you must enable the feature on these entries:
-
/chatops run feature set --project=mgandres1/test-ci-project ci_retry_downstream_pipeline true
-
/chatops run feature set --project=gitlab-org/gitlab ci_retry_downstream_pipeline true
-
/chatops run feature set --project=gitlab-org/gitlab-foss ci_retry_downstream_pipeline true
-
/chatops run feature set --project=gitlab-com/www-gitlab-com ci_retry_downstream_pipeline true
-
Preparation before global rollout
-
Ensure that documentation has been updated (More info).
Global rollout on production
Incrementally roll out the feature.
- If the feature flag in code has an actor, perform actor-based rollout.
-
/chatops run feature set ci_retry_downstream_pipeline 25 --actors
-
/chatops run feature set ci_retry_downstream_pipeline 50 --actors
-
/chatops run feature set ci_retry_downstream_pipeline 75 --actors
-
/chatops run feature set ci_retry_downstream_pipeline 100 --actors
-
Enable feature by default, so self-managed has access to the feature. <- This is an MR, so the date refers to merging date.
-
-
Announce on the feature issue that the feature has been globally enabled. -
Wait for at least one day for the verification term.
%14.9, dates TBD.
Release the feature - This cleanup work will be done after-
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_retry_downstream_pipeline --dev
-
/chatops run feature delete ci_retry_downstream_pipeline --staging
-
/chatops run feature delete ci_retry_downstream_pipeline
-
-
Close this rollout issue.
Rollback Steps
-
This feature can be disabled by running the following Chatops command:
/chatops run feature set ci_retry_downstream_pipeline false
Edited by Laura Montemayor