Repository navigation
ci: raise the merge queue's build concurrency from 2 to 4 - #6391
Merged
andygrove merged 1 commit intoSep 29, 2026
Merged
Conversation
With two merge_group builds in flight and a median full pipeline of 92 minutes, a queue that never runs dry tops out at roughly 30 merges a day, while approvals have been arriving at about 20 a day and merges landing at about 13.6. Four builds in flight roughly doubles the cap. Also correct the comment on the merge_group diff in ci.yml: merge_group.base_sha is the queue commit of the entry ahead, not main, so each entry's build covers only its own changes. That is sound under ALLGREEN and is why HEADGREEN would not be, which the .asf.yaml comment now says too. The contributor guide described the queue as batching up to five pull requests into one build; it builds each entry on top of the ones ahead of it instead. Closes apache#6386.
github-actions
Bot
added
build
andygrove
enabled auto-merge
September 29, 2026 14:23
Member
Author
|
Thanks @mbutrovich! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #6386.
Rationale for this change
The merge queue builds at most two entries at once. With a median full pipeline of 92 minutes (2026-09-11 to 2026-09-29), that caps a queue that never runs dry at roughly 30 merges a day. Approvals have been arriving at about 20 a day and merges landing at about 13.6, so the approved backlog keeps growing, and a batch of queued PRs takes 10 to 12 hours to drain. The data, and a simulation of other settings, are in the issue.
What changes are included in this PR?
.asf.yaml:max_entries_to_buildgoes from 2 to 4, and its comment carries the current numbers.merge_groupdiff inci.ymlsaidbase_shacovers every entry batched into the group. It is the queue commit of the entry ahead, so each entry's build covers only its own changes. TheALLGREENcomment in.asf.yamlnow says why that makesHEADGREENunsafe.ci.mddescribed the queue as building up to five pull requests as one batch. It now describes the per-entry builds..github/workflows/README.mdgets the new numbers.How are these changes tested?
python3 dev/ci/check-ci-config.py,actionlintand prettier pass locally. The ruleset change takes effect when ASF's.asf.yamlprocessing applies it after the merge; the queue's GraphQLconfiguration.maximumEntriesToBuildshould then read 4.