## Summary Roll out [the feature](https://gitlab.com/gitlab-org/gitlab/-/work_items/627944) currently behind the `dap_unfiltered_clone` feature flag. - DRI: @bastirehm - Team Slack channel: `#g_agent-execution` > [!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? Unfiltered clones fetch full blob history instead of a blobless partial clone, so the initial transfer is larger. On very large repositories or heavy clone traffic this could increase Gitaly/Packhorse load or slow session startup instead of reducing it, which is the opposite of the intended effect. Monitor Gitaly pack-objects saturation and `ResourceExhausted` rates closely when enabling for high-traffic projects (see !254676). ## Events - [Exceptions with dap_unfiltered_clone: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:%22dap_unfiltered_clone:1%22'),columns:!(json.exception.class,json.exception.message,json.extra.workflow_id,json.meta.caller_id),sort:!(!(json.time,desc)))) - [Events with dap_unfiltered_clone: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:%22dap_unfiltered_clone: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_agent-execution`. 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 dap_unfiltered_clone 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set dap_unfiltered_clone true --dev --pre --staging --staging-ref ``` **Production** — target specific high-traffic projects first (per-project actor flag), then a percentage rollout only if broader roll out is decided (wait ≥15 min between steps, watch dashboards): ``` /chatops gitlab run feature set --project=gitlab-org/gitlab dap_unfiltered_clone true ``` ``` /chatops gitlab run feature set dap_unfiltered_clone <percentage> --actors ``` Or target additional actors: ``` /chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss dap_unfiltered_clone true /chatops gitlab run feature set --group=gitlab-org,gitlab-com dap_unfiltered_clone true /chatops gitlab run feature set --user=<gitlab-username-of-dri> dap_unfiltered_clone 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 updated - [ ] Breaking changes announced, if any - [ ] Change management issue opened, if required - [ ] External API consumers handled with a fail-open mechanism, if applicable - [ ] Gitaly pack-objects saturation / `ResourceExhausted` rates confirmed stable after enabling for `gitlab-org/gitlab` (see rollout checklist in !254676) - [ ] Default clone strategy decided (keep blobless default, or make unfiltered the default and remove the flag) ## Cleanup Remove the flag once deemed stable — 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. 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 dap_unfiltered_clone --dev --pre --staging --staging-ref --production ``` ## Rollback ``` /chatops gitlab run feature set dap_unfiltered_clone false # production /chatops gitlab run feature set dap_unfiltered_clone false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete dap_unfiltered_clone --dev --pre --staging --staging-ref --production # remove entirely ```