[Feature flag] Rollout of `variables_in_include_section_ci`

What

Rollout of feature variables_in_include_section_ci

Owners

• Team: groupcompliance
• Most appropriate slack channel to reach out to: #g_compliance
• Best individual to reach out to: @asubramanian1

Expectations

What are we expecting to happen?

When the flag is enabled, pre-defined project variables can be used in the include section of .gitlab-ci.yml

What might happen if this goes wrong?

Could affect the running of CI pipelines

What can we monitor to detect problems with this?

Roll Out Steps

• Confirm that QA tests pass with the feature flag enabled (if you're unsure how, contact the relevant stable counterpart in the Quality department)
• Enable on staging (/chatops run feature set feature_name true --staging)
• Test on staging
• Ensure that documentation has been updated
• [-] Enable on GitLab.com for individual groups/projects listed above and verify behaviour (/chatops run feature set --project=gitlab-org/gitlab feature_name true) -NA- as the FF is global
• Coordinate a time to enable the flag with the SRE oncall and release managers
  • In #production mention @sre-oncall and @release-managers. Once an SRE on call and Release Manager on call confirm, you can proceed with the rollout
• Announce on the issue an estimated time this will be enabled on GitLab.com
• Enable on GitLab.com by running chatops command in #production (/chatops run feature set feature_name true)
• Cross post chatops Slack command to #support_gitlab-com (more guidance when this is necessary in the dev docs) and in your team channel
• Announce on the issue that the flag has been enabled
• Remove feature flag and add changelog entry (!52108 (merged))
• After the flag removal is deployed, clean up the feature flag by running chatops command in #production channel

Rollback Steps

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

/chatops run feature set --project=gitlab-org/gitlab feature_name false