Rollout of same_stage_job_needs
Feature
This feature uses the ci_same_stage_job_needs
feature flag
Owners
- Team: grouppipeline authoring
- Most appropriate slack channel to reach out to:
#g_pipeline_authoring
- Best individual to reach out to: @lauraMon
- PM: @dhershkovitch
The Rollout Plan
Preparation Phase
-
07/19 - Enable on staging ( /chatops run feature set ci_same_stage_job_needs true --staging
) -
Test on staging -
07/21 - Enable it for gitlab-org/gitlab
-
Test -
07/28 - Enable it for 25% of Gitlab.com -
Test -
07/29 - Enable it for 50% of Gitlab.com -
Test -
07/30 - Enable it for 75% of Gitlab.com
REVERTED on 08/02
Updated timeline:
-
08/10 - Enable it for gitlab-org/gitlab
-
Test -
08/10 - Enable it for 100% of Gitlab.com -
Test -
08/11 or 12 - Enable it by default in the YAML file - this depends on when the MR is merged, so it might be a few days after. -
Ensure that documentation has been updated
Cleanup
-
Announce on the issue that the flag has been enabled -
Remove ci_same_stage_job_needs
feature flag-
Remove all references to the feature flag from the codebase -
Remove the YAML definitions for the feature from the repository -
Create a Changelog Entry
-
-
Clean up the feature flag from all environments by running this chatops command in #production
channel/chatops run feature delete some_feature
.
Final Step
-
Close this rollout issue for the feature flag after the feature flag is removed from the codebase. - [-] Follow-up 1 - this has its own separate issue
Rollback Steps
-
This feature can be disabled by running the following Chatops command:
/chatops run feature set --project=gitlab-org/gitlab ci_same_stage_job_needs false