[Feature flag] Rollout of `ci_quota_check_on_retries`

Summary

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

• !62702 (merged)
• https://gitlab.com/gitlab-org/gitlab/-/issues/323486

Owners

• Team: grouppipeline execution
• Most appropriate slack channel to reach out to: #g_pipeline_execution
• Best individual to reach out to: @mbobin
• PM: @jreporter

The Rollout Plan

• Partial Rollout on GitLab.com with testing groups
• Percentage Rollout on GitLab.com

Testing Groups/Projects/Users

• gitlab-org/gitlab project
• sandbox-qa/test-323486 project

Expectations

What are we expecting to happen?

Users should not be able to retry jobs/pipelines if they are out of CI minutes.

What might happen if this goes wrong?

The feature flag should be turned off.

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 ci_quota_check_on_retries true --dev
  • /chatops run feature set ci_quota_check_on_retries 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 flag in code has an actor, enable it on GitLab.com for testing groups/projects.
  • /chatops run feature set --<actor-type>=<actor> ci_quota_check_on_retries true
• Verify that the feature works as expected. Posting the QA result in this issue is preferable.

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_quota_check_on_retries <rollout-percentage> --actors
  • Enable the feature globally on production environment.
    • /chatops run feature set <feature-flag-name> true
• Announce on the feature issue that the feature has been globally enabled.
• Cross-post chatops slack command to #support_gitlab-com. (more guidance when this is necessary in the dev docs) and in your team channel
• 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 ci_quota_check_on_retries 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 above 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 2885943e
• 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_quota_check_on_retries --dev
  • /chatops run feature delete ci_quota_check_on_retries --staging
  • /chatops run feature delete ci_quota_check_on_retries
• Close this rollout issue.

Rollback Steps

• This feature can be disabled by running the following Chatops command:

/chatops run feature set ci_quota_check_on_retries false