GitLab Next

What

Remove the :group_coverage_data_report_graph feature flag ...

Owners

• Team: Testing
• Most appropriate slack channel to reach out to: #g_testing
• Best individual to reach out to: @shampton, @morefice, @jheimbuck_gl, @mfluharty

Expectations

What are we expecting to happen?

Should show a section on the group repositories analytics page to show the latest code coverage activity data for the group.

Should also enable a GraphQL API for codeCoverageActivities in a group.

What might happen if this goes wrong?

The section does not work properly, or the GraphQL API doesn't work as expected.

What can we monitor to detect problems with this?

If we can monitor the API for response times that should be sufficient (or load time on the page even better).

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-com groups

Roll Out Steps

• 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)
• Enable on GitLab.com by running chatops command in #production (/chatops run feature set feature_name true)
• 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