[new_pipeline_form] Roll out plan

What

In !35674 (merged) the pipelines/new form was refactored from HAML to Vue. Once this feature is deemed stable in Vue, we should remove the feature flag new_pipeline_form and all related code.

Owners

• Team: ~"group::continuous integration"
• Most appropriate slack channel to reach out to: #g_ci
• Best individual to reach out to: @pburdette

Expectations

What are we expecting to happen?

What might happen if this goes wrong?

What can we monitor to detect problems with this?

Beta groups/projects

If applicable, any groups/projects that are happy to have this feature turned on early. Some organizations may wish to test big changes they are interested in with a small subset of users ahead of time for example.

• gitlab-org/gitlab project
• gitlab-org/gitlab-com groups
• ...

Roll Out Steps

• Enable on staging
• Test on staging
• [-] Ensure that documentation has been updated
  • No need, this feature is an equivalent HAML to Vue port.
• Enable on GitLab.com for individual groups/projects listed above and verify behaviour
  • Used 25% rollout /chatops run feature set new_pipeline_form 25 --actors
  • Used 50% rollout /chatops run feature set new_pipeline_form 50 --actors
  • Used 75% rollout /chatops run feature set new_pipeline_form 75 --actors
• Coordinate a time to enable the flag with #production and #g_delivery on slack.
• Announce on the issue an estimated time this will be enabled on GitLab.com
• Enable on GitLab.com by running chatops command in #production
• 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
• After the flag removal is deployed, clean up the feature flag by running chatops command in #production channel
• Remove all related code
  • Consider code here: #321847 (comment 511172952)