[ci_build_tags_limit] Rollout build tags limit to prevent pipeline creation with more than 50 tags

Summary

This issue is to rollout build tags limits on production, which is currently behind the ci_build_tags_limit feature flag.

Owners

• Team: grouppipeline execution
• Most appropriate slack channel to reach out to: #g_pending_builds_table
• Best individual to reach out to: @morefice @jreporter

Expectations

What are we expecting to happen?

Pipeline should fail if a build has more than 50 tags.

What might happen if this goes wrong?

Pipeline processing could be broken for build with more than 50 tags.

What can we monitor to detect problems with this?

• https://dashboards.gitlab.net/d/stage-groups-pipeline_execution/stage-groups-group-dashboard-verify-pipeline-execution?orgId=1

What can we monitor to detect problems with this?

Sentry, PostgreSQL triage dashboard.

Rollout Steps

• Enable the FF fully on Staging
  • /chatops run feature set ci_build_tags_limit true --staging
• Enable for 5% of calls on gitlab.com
  • /chatops run feature set ci_build_tags_limit 5
• Enable for 10% of calls on gitlab.com
  • /chatops run feature set ci_build_tags_limit 10
• Enable for 50% of calls on gitlab.com
  • /chatops run feature set ci_build_tags_limit 50
• Enable for 100% of calls on gitlab.com
  • /chatops run feature set ci_build_tags_limit 100
  • /chatops run feature set ci_build_tags_limit true

Rollback Steps

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

/chatops run feature set ci_build_tags_limit 0
/chatops run feature set ci_build_tags_limit false

cc @grzesiek @mbobin @jreporter