[Feature flag] Rollout of `ci_value_change_for_processable_and_rules_entry`

Summary

This issue is to rollout !90238 (merged) on production, that is currently behind the ci_value_change_for_processable_and_rules_entry feature flag.

Owners

• Team: grouppipeline authoring
• Most appropriate slack channel to reach out to: #g_pipeline-authoring
• Best individual to reach out to: @furkanayhan
• PM: @dhershkovitch

Expectations

What are we expecting to happen?

We expect nothing to change because it is a refactoring.

What might happen if this goes wrong?

Rules may be evaluated wrongly and some jobs are not created while they need to be, or vice versa.

We can safely disable the feature flag.

What can we monitor to detect problems with this?

• We should not see a decrease of 201 response code of Projects::PipelinesController#create endpoint: https://log.gprd.gitlab.net/goto/7d638af810e4b002de03d9df7132175c
• We should not see an increase of pipeline creation errors via PostReceive: https://log.gprd.gitlab.net/goto/1f47665f46009eab2b3e142a251ac17c
  • This metric is not enough itself because it is just a number. We should provide a metric like; errors / total number of enqueued workers PostReceive. Help?
  • For now; compare it with: https://log.gprd.gitlab.net/goto/542b35f80796baf5163d870af8796391

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_value_change_for_processable_and_rules_entry true --dev --staging
• 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.

Global rollout on production

• Announce on the feature issue that the feature has been globally enabled.
• Wait for at least one day for the verification term.

Release the feature

• Create a merge request to remove ci_value_change_for_processable_and_rules_entry 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 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 <merge-request-url> <milestone>
• 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 feature delete ci_value_change_for_processable_and_rules_entry --dev --staging --production
• Close this rollout issue.

Rollback Steps

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

/chatops run feature set ci_value_change_for_processable_and_rules_entry false