[Feature flag] Rollout of `ci_new_public_oss_cost_factor`

Summary

This issue is to rollout the feature on production, that is currently behind the ci_new_public_oss_cost_factor feature flag.

Owners

  • Team: Pipeline Execution
  • Most appropriate slack channel to reach out to: #g_pipeline_execution
  • Best individual to reach out to: @allison.browne
  • PM: @jheimbuck_gl

Stakeholders

Expectations

What are we expecting to happen?

When is the feature viable?

What might happen if this goes wrong?

What can we monitor to detect problems with this?

Consider mentioning checks for 5xx errors or other anomalies like an increase in redirects (302 HTTP response status)

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 <merge-commit-of-your-feature>
  • Enable the feature globally on non-production environments.
    • /chatops run feature set ci_new_public_oss_cost_factor true --dev --staging --staging-ref
  • Verify that the feature works as expected. Posting the QA result in this issue is preferable. The best environment to validate the feature in is staging-canary as this is the first environment deployed to. Note you will need to make sure you are configured to use canary as outlined here when accessing the staging environment in order to make sure you are testing appropriately.

Specific rollout on production

  • Ensure that the feature MRs have been deployed to both production and canary.
    • /chatops run auto_deploy status <merge-commit-of-your-feature>
  • If you're using project-actor, you must enable the feature on these entries:
    • /chatops run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss,gitlab-com/www-gitlab-com ci_new_public_oss_cost_factor true
  • If you're using group-actor, you must enable the feature on these entries:
  • Verify that the feature works on the specific entries. Posting the QA result in this issue is preferable.

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_pipeline_execution).

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.

You can either create a follow-up issue for Feature Flag Cleanup or use the checklist below in this same issue.

  • Create a merge request to remove ci_new_public_oss_cost_factor 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.
    • Ask for review and merge it.
  • Ensure that the cleanup MR has been included in the release package. If the merge request was deployed before the monthly release was tagged, the feature can be officially announced in a release blog post.
    • /chatops run release check 9cc487cf
  • Close the feature issue to indicate the feature will be released in the current milestone.
  • If not already done, clean up the feature flag from all environments by running these chatops command in #production channel:
    • /chatops run auto_deploy status 9cc487cf6944f15423f5cc94dd965ec37c1dd37f
    • /chatops run feature delete ci_new_public_oss_cost_factor --dev --staging --staging-ref --production
  • Close this rollout issue.

Rollback Steps

  • This feature can be disabled by running the following Chatops command:
/chatops run feature set ci_new_public_oss_cost_factor false
Edited by Allison Browne