## Summary Roll out [the feature](https://gitlab.com/groups/gitlab-org/-/work_items/21610) currently behind the `show_duo_mr_risk_classification_widget` feature flag. - DRI: @wanpol - Team Slack channel: `#g_code-review` > [!note] > Process and guidance live in the docs — this issue is just the commands and a place to track the rollout. > "Rolling out" means incrementally enabling the flag on GitLab.com to validate stability — it is not the same as releasing the feature, which happens when the flag is removed. > [Feature flag controls](https://docs.gitlab.com/development/feature_flags/controls/) · [Feature flag lifecycle](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) ## What could go wrong? The worst case is low. Reviewers may see a risk level, confidence score, or rationale that is wrong or out of date. Each merge request page view sends one extra GraphQL query, which adds a small load to that endpoint. The widget also needs the `duo_mr_risk_classification` flag on and an existing risk assessment, so this only affects projects that already run risk classification. If we see problems, we turn the flag off and the widget disappears right away. No data changes and merges are not blocked. Dashboards to watch: merge request page and GraphQL latency on https://dashboards.gitlab.net. ## Events - [Exceptions with show_duo_mr_risk_classification_widget:1](https://log.gprd.gitlab.net/app/discover#/?_g=(time:(from:now-1d,to:now))&_a=(index:'7092c4e2-4eb5-46f2-8305-a7da2edad090',query:(language:kuery,query:'json.exception.feature_flag_states.keyword:%22show_duo_mr_risk_classification_widget:1%22'),columns:!(json.exception.class,json.exception.message,json.extra.workflow_id,json.meta.caller_id),sort:!(!(json.time,desc)))) - [Events with show_duo_mr_risk_classification_widget:1](https://log.gprd.gitlab.net/app/discover#/?_g=(time:(from:now-1d,to:now))&_a=(index:'7092c4e2-4eb5-46f2-8305-a7da2edad090',query:(language:kuery,query:'json.feature_flag_states:%22show_duo_mr_risk_classification_widget:1%22'),columns:!(json.meta.caller_id,json.feature_flag_states),sort:!(!(json.time,desc)))) - [Error rate and other graphs by modifying the examples in the Visualization Library](https://log.gprd.gitlab.net/app/visualize#/?_g=h@358d019&s=FF%20Observability) Feature Flag events are only logged by default for feature flags marked for the current or future milestones. To enable while the feature flag is active, see https://docs.gitlab.com/development/feature_flags/#logging ## Rollout Run all production `/chatops` in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `#g_code-review`. Background: [incremental rollout process](https://docs.gitlab.com/development/feature_flags/controls/#process), [feature actors](https://docs.gitlab.com/development/feature_flags/#feature-actors). **Non-production** ``` /chatops gitlab run feature set show_duo_mr_risk_classification_widget 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set show_duo_mr_risk_classification_widget true --dev --pre --staging --staging-ref ``` **Production** — percentage rollout (wait ≥15 min between steps, watch dashboards): ``` /chatops gitlab run feature set show_duo_mr_risk_classification_widget <percentage> --actors ``` Or target specific actors instead: ``` /chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss show_duo_mr_risk_classification_widget true /chatops gitlab run feature set --group=gitlab-org,gitlab-com show_duo_mr_risk_classification_widget true /chatops gitlab run feature set --user=wanpol show_duo_mr_risk_classification_widget true ``` ## Before global rollout Confirm the relevant gotchas before going to 100% — see [enabling a feature for GitLab.com](https://docs.gitlab.com/development/feature_flags/controls/#enabling-a-feature-for-gitlabcom): - [Docs + version history](https://docs.gitlab.com/development/documentation/feature_flags/) updated - [Breaking changes](https://docs.gitlab.com/development/documentation/release_notes/#deprecations-removals-and-breaking-changes) announced, if any - [Change management issue](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/#feature-flags-and-the-change-management-process) opened, if required - [External API consumers](https://docs.gitlab.com/development/feature_flags/#do-not-use-feature-flags-in-external-api-consumers) handled with a fail-open mechanism, if applicable ## Cleanup Remove the flag once [deemed stable](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) — see [cleaning up](https://docs.gitlab.com/development/feature_flags/controls/#cleaning-up). Track it here, or open a follow-up [Feature Flag Cleanup issue](https://gitlab.com/gitlab-org/gitlab/-/work_items/new?description_template=Feature%20Flag%20Cleanup). Remove the flag and its YAML definition from the codebase, then: ``` /chatops gitlab run release check https://gitlab.com/gitlab-org/gitlab/-/merge_requests/256392 19.5 /chatops gitlab run feature delete show_duo_mr_risk_classification_widget --dev --pre --staging --staging-ref --production ``` ## Rollback ``` /chatops gitlab run feature set show_duo_mr_risk_classification_widget false # production /chatops gitlab run feature set show_duo_mr_risk_classification_widget false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete show_duo_mr_risk_classification_widget --dev --pre --staging --staging-ref --production # remove entirely ```