## Summary Roll out [the feature](https://gitlab.com/gitlab-org/gitlab/-/work_items/611125) currently behind the `ci_create_pipeline_worker_retry_on_commit_not_found` feature flag. - DRI: @furkanayhan - Team Slack channel: `#g_pipeline-authoring` > [!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 makes a transient `"Commit not found"` error during push pipeline creation retryable via Sidekiq (`retry: 3`) instead of being silently dropped. Blast radius is limited to `CreatePipelineWorker`; a genuinely-invalid commit would now retry up to 3 times before being logged, but the transient signature (`ref_exists?` true but `sha` nil) makes this almost always a read-after-write miss. **Caveat:** `TransientGitalyReadError` subclasses `Gitlab::SidekiqMiddleware::RetryError`, which is suppressed from Sentry and excluded from the Sidekiq execution SLI. So these retries will **not** trip the usual error alerts — don't expect Sentry to surface them. The two signals that actually matter are `sidekiq_jobs_failed_total` climbing without recovery, and the exhausted-retry log volume rising (pipelines not self-healing within 3 retries). ### How to monitor 1. `json.class.keyword: "CreatePipelineWorker" and json.exception.message.keyword: "Commit not found"` Transient "Commit not found" misses that were caught and retried. A rise here at rollout is expected — it just means the flag is now catching these instead of silently dropping the pipeline. These should self-heal within the 3 retries. https://log.gprd.gitlab.net/app/r/s/XFjGQ 2. `json.class.keyword: "CreatePipelineWorker" and json.message.keyword: "Error creating pipeline" and json.errors.keyword : "Commit not found"` Pipelines that did NOT self-heal — still "Commit not found" after all 3 retries were exhausted. This is the key signal to watch; it should stay near-zero. A rise means pipelines are still being dropped despite the retries. https://log.gprd.gitlab.net/app/r/s/IVvWH ## Rollout Run all production `/chatops` in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `#g_pipeline-authoring`. 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 ci_create_pipeline_worker_retry_on_commit_not_found 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set ci_create_pipeline_worker_retry_on_commit_not_found true --dev --pre --staging --staging-ref ``` **Production** — percentage rollout (wait ≥15 min between steps, watch dashboards): ``` /chatops gitlab run feature set ci_create_pipeline_worker_retry_on_commit_not_found <percentage> --actors ``` Or target specific actors instead: ``` /chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss ci_create_pipeline_worker_retry_on_commit_not_found true /chatops gitlab run feature set --group=gitlab-org,gitlab-com ci_create_pipeline_worker_retry_on_commit_not_found true /chatops gitlab run feature set --user=furkanayhan ci_create_pipeline_worker_retry_on_commit_not_found 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 ci_create_pipeline_worker_retry_on_commit_not_found --dev --pre --staging --staging-ref --production ``` ## Rollback ``` /chatops gitlab run feature set ci_create_pipeline_worker_retry_on_commit_not_found false # production /chatops gitlab run feature set ci_create_pipeline_worker_retry_on_commit_not_found false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete ci_create_pipeline_worker_retry_on_commit_not_found --dev --pre --staging --staging-ref --production # remove entirely ```