<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=604110) </details> <!--IssueSummary end--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=604110) </details> ## Summary Roll out [the feature](https://gitlab.com/gitlab-org/gitlab/-/work_items/591805) currently behind the `arkose_labs_signup_challenge_loading_state` feature flag. - DRI: @kgreif - Team Slack channel: `#g_acquisition` > [!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? Functionality has been tested on staging: {width=900 height=507} ## Rollout Run all production `/chatops` in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `#g_acquisition`. 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 arkose_labs_signup_challenge_loading_state 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set arkose_labs_signup_challenge_loading_state true --dev --pre --staging --staging-ref ``` **Production** — percentage rollout (wait ≥15 min between steps, watch dashboards): 1. Tuesday 7am UTC: 5% actors ``` /chatops gitlab run feature set arkose_labs_signup_challenge_loading_state 5 --actors ``` 2. Tuesday 9am UTC: 10% actors ``` /chatops gitlab run feature set arkose_labs_signup_challenge_loading_state 10 --actors ``` 3. Tuesday 11am UTC: 25% actors ``` /chatops gitlab run feature set arkose_labs_signup_challenge_loading_state 25 --actors ``` 4. Tuesday 1pm UTC: 50% actors ``` /chatops gitlab run feature set arkose_labs_signup_challenge_loading_state 50 --actors ``` 5. Wednesday 7am UTC: fully enable ``` /chatops gitlab run feature set arkose_labs_signup_challenge_loading_state true ``` **What to monitor:** - Controller logs - Sentry - Grafana request and error rates Or target specific actors instead: ``` /chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss arkose_labs_signup_challenge_loading_state true /chatops gitlab run feature set --group=gitlab-org,gitlab-com arkose_labs_signup_challenge_loading_state true /chatops gitlab run feature set --user=kgreif arkose_labs_signup_challenge_loading_state 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/-/issues/new?description_template=Feature%20Flag%20Cleanup). Remove the flag and its YAML definition from the codebase, then: ``` /chatops gitlab run release check <merge-request-url> <milestone> /chatops gitlab run feature delete arkose_labs_signup_challenge_loading_state --dev --pre --staging --staging-ref --production ``` ## Rollback ``` /chatops gitlab run feature set arkose_labs_signup_challenge_loading_state false # production /chatops gitlab run feature set arkose_labs_signup_challenge_loading_state false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete arkose_labs_signup_challenge_loading_state --dev --pre --staging --staging-ref --production # remove entirely ```