## Summary Issue link: https://gitlab.com/gitlab-org/gitlab/-/work_items/631374 Roll out [the feature](https://gitlab.com/gitlab-org/gitlab/-/issues/627233) currently behind the `lock_concurrent_pipeline_retries` feature flag. - DRI: @srajadas - Team Slack channel: `#g_pipeline_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? The flag prevents concurrent retries of the same pipeline by taking a Redis exclusive lease and returning a `409 Conflict` response if a second retry is attempted while one is in progress. The worst case is rejecting a retry that should have been allowed. There is no data loss. The lease is keyed on the pipeline ID, so one pipeline's retry cannot affect another's. Only the user-facing entry points are affected: the REST endpoint `POST /api/:version/projects/:id/pipelines/:pipeline_id/retry`, the GraphQL `PipelineRetry` mutation, and the web UI. Housekeeping paths (automatic pipeline cleanup, project deletion) use a separate code path and are not affected. Watch the `409` rate on `json.route.keyword: "/api/:version/projects/:id/pipelines/:pipeline_id"` with `json.method: POST`, and the `json.error_reason` field for `retry_in_progress`. Rejections should be close to zero at the current thresholds. The lock timeout is 1 minute (matching the Rack request timeout), so any `409` indicates a genuine concurrent retry attempt. ## Events - [Exceptions with lock_concurrent_pipeline_retries: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:%22lock_concurrent_pipeline_retries:1%22'),columns:!(json.exception.class,json.exception.message,json.extra.workflow_id,json.meta.caller_id),sort:!(!(json.time,desc)))) - [Events with lock_concurrent_pipeline_retries: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:%22lock_concurrent_pipeline_retries: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_pipeline_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** ``` gitlab run feature set lock_concurrent_pipeline_retries 50 --actors --dev --pre --staging --staging-ref gitlab run feature set lock_concurrent_pipeline_retries true --dev --pre --staging --staging-ref ``` **Production** — percentage rollout (wait ≥15 min between steps, watch dashboards): ``` gitlab run feature set lock_concurrent_pipeline_retries <percentage> --actors ``` Or target specific actors instead: ``` gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss lock_concurrent_pipeline_retries true gitlab run feature set --group=gitlab-org,gitlab-com lock_concurrent_pipeline_retries true gitlab run feature set --user=srajadas lock_concurrent_pipeline_retries 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: ``` gitlab run release check https://gitlab.com/gitlab-org/gitlab/-/merge_requests/258575 19.5 gitlab run feature delete lock_concurrent_pipeline_retries --dev --pre --staging --staging-ref --production ``` ## Rollback ``` gitlab run feature set lock_concurrent_pipeline_retries false # production gitlab run feature set lock_concurrent_pipeline_retries false --dev --pre --staging --staging-ref # non-production gitlab run feature delete lock_concurrent_pipeline_retries --dev --pre --staging --staging-ref --production # remove entirely ```