[Feature flag]: Enable new pipeline graph 😬

aka, the Pipeline Graph Structural Update Rollout

What

Enable the :graphql_pipeline_details feature flag. See #276949 (closed) for details of this project.

Owners

• Team: Verify:Pipeline Authoring
• Most appropriate slack channel to reach out to: #g_ci-pa-engineering
• Best individual to reach out to: @sarahghp (also @samdbeckham and @f_caplette might be able to help)

Expectations

What are we expecting to happen?

We expect a graph that looks like this to replace the current pipeline graph.

What might happen if this goes wrong?

The worst outcome would be users being unable to see the graphs for their running pipelines. Other failures would include linked pipeline expansion failure, UI failures in either the new or old graph, poor performance in link drawing. While it's possible actions could fail, that would be very unexpected, as that code is untouched, except for polling changes.

What can we monitor to detect problems with this?

– Sentry alerts: #294028 (closed)
– Link generation performance (maybe, see #281351 (closed))

I am in a beta and I found a bug. What should I do?

First off, you are awesome and we really appreciate your help. Please open an issue and assign it to @sarahghp for further triage.

Beta groups/projects

• Individual volunteers
• gitlab-org/gitlab-ui project
• gitlab-org/gitlab project
• gitlab-org/gitlab-com groups

Roll Out Steps

• Rollout to beta testers (2021-01-22)
• Rollout to Gitlab UI project (2021-03-04)
• Rollout to Gitlab project (2021-03-04)
• Enable on staging (/chatops run feature set feature_name true --staging)(2021-03-04)
• Test on staging (2021-03-04)
• Confirm that QA tests pass with the feature flag enabled (if you're unsure how, contact the relevant stable counterpart in the Quality department) (2021-03-25)
• Ensure that documentation has been updated (see #276949 (comment 488320792) for what to update)
• Enable on GitLab.com for individual groups/projects listed above and verify behaviour (/chatops run feature set --project=gitlab-org/gitlab feature_name true)
• 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 (100% to dot-com on 2021-04-06)
• 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 (expected to be done in 14.0)
• After the flag removal is deployed, clean up the feature flag by running chatops command in #production channel (expected to be done in 14.0)

Rollback Steps

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

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