[Feature flag] ci_validate_job_length

[Feature flag] ci_validate_job_length

Summary

This issue is to rollout the feature on production, that is currently behind the ci_validate_job_length feature flag. This feature flag is enabled by default, as the intention of the feature flag is to be mindful of self-managed. The flag will then be removed and a database validation added.

Owners

• Team: Pipeline Authoring
• Most appropriate slack channel to reach out to: #g_pipeline_authoring
• Best individual to reach out to: @lauraX
• PM: @dhershkovitch

Rollout Steps

Release the feature

• Create a merge request to remove ci_validate_job_length 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_validate_job_length
• Close this rollout issue.

Rollback Steps

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

/chatops run feature set ci_validate_job_length false