[smart_cobertura_parser] Enable smart cobertura parser feature
What
Remove the :smart_cobertura_parser
feature flag.
Related work: !48048 (merged)
Owners
- Team: grouptesting
- Most appropriate slack channel to reach out to:
#g_testing
- Best individual to reach out to: @iamricecake @rickywiens
Expectations
What are we expecting to happen?
Once the feature flag is enabled, the projects (mostly C# and Java ones) will now be able to use the cobertura coverage diff feature because this enables the fix on the cobertura parser to properly match the files to the paths. More details of the fix on !48048 (merged).
Existing projects that have the cobertura parsing already working for them will not see or experience any changes.
What might happen if this goes wrong?
If we encounter errors on the parsing then inline coverage report indicators on the MR diff won't show up.
If we see a significant increase in execution time, then it will take some time to show the inline indicators on the MR diff.
What can we monitor to detect problems with this?
Monitor for significant increase in errors or execution time in the dashboard.
We can also look for unexpected errors that are not related to invalid XML format on sentry.
We also can monitor if there's a significant increase in duration of parsing on thanos.
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
-
Implement monitoring #284843 (closed) -
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 smart_cobertura_parser 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
- In
-
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 smart_cobertura_parser 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 -
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 smart_cobertura_parser false