You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Queued changes wait up to 15 minutes after validation for earlier production deploys #6139
On 12 November, 7 of 16 successful merge-queue CI runs that deployed to production had to wait for the entries ahead of them to deploy first. The wait is the 🧾 Wait until the candidate is first on current main step. It starts about 20 seconds into the run and runs alongside validation, so it only delays the deploy by the part that outlasts validation:
The other 9 runs waited 17–24 s, and their deploy started as soon as validation finished. Each production deploy job took 630–1,144 s (637–825 s in the afternoon runs).
Problem
Production deploys run one at a time, and every merged change gets its own deploy. In a busy queue, a change that has finished its own validation can sit for up to one deploy per entry ahead of it: up to 15 minutes in the runs above. #5495 made validation and the deploy itself faster, so this queueing is now the largest variable part of the time from queueing a change to having it live.
Hypothesis and success signal
Fewer deploys per queued change should cut the delay without weakening any check. There are two independent levers:
Success: across at least ten comparable busy-period runs, the delay between an entry finishing validation and starting its deploy drops well below the current 92–876 s for entries that were not first in the queue. Every required check still runs, and a failed deploy still names the change that caused it.
Acceptance criteria
Decide which lever to try first and record why, including what happens to the per-change checks under that lever.
Ship it behind the existing required checks, with no check removed or skipped for a change that touches deployed manifests.
#6036 - ci: preserve production deploy order while merge groups validate [merged]
📝 Issue Planner
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Activity
coderabbitai commentedon Nov 12, 2026
🔗 Related PRs
#6036 - ci: preserve production deploy order while merge groups validate [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!