Closed Bug 684436 Opened 11 years ago Closed 11 years ago

Stop merging builds for pushes within 3 minutes of each other

Categories

(Release Engineering :: General, defect, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: catlee)

Details

Attachments

(1 file)

Tonight makes two nights in a row where mozilla-inbound has had bustage, but yet excessive numbers of changesets have had to be backed out, since their builds have been combined (due to being within 3 minutes of each other).

Mak, myself and others certain others sherrifing m-i feel that the advantages of coalescing builds within 3 minutes is vastly outweighed by the confusion of blame.

Yes, it may rarely save one extra build, but more frequently it results in numerous extra builds after backing out one changeset after another, in order to find the cause of bustage.

Please can this be stopped.
I've asked this a number of times in the past.  Releng has always said that the extra load might be too high for them to handle.  Is there any way for us to measure exactly how much this is saving us, and what would happen if we avoided job coalescing at least on mozilla-inbound?
(In reply to Ehsan Akhgari [:ehsan] from comment #1)
> I've asked this a number of times in the past.  Releng has always said that
> the extra load might be too high for them to handle.  Is there any way for
> us to measure exactly how much this is saving us, and what would happen if
> we avoided job coalescing at least on mozilla-inbound?

FTR, I think it should be fine. Also, we're likely to coalesce changes that happen within the same poll interval, which is 60s right now.
(In reply to Chris AtLee [:catlee] from comment #2)
> (In reply to Ehsan Akhgari [:ehsan] from comment #1)
> > I've asked this a number of times in the past.  Releng has always said that
> > the extra load might be too high for them to handle.  Is there any way for
> > us to measure exactly how much this is saving us, and what would happen if
> > we avoided job coalescing at least on mozilla-inbound?
> 
> FTR, I think it should be fine. Also, we're likely to coalesce changes that
> happen within the same poll interval, which is 60s right now.

By "it", do you mean not coalescing jobs in the 3-minute window?
Assignee: nobody → catlee
Priority: -- → P2
Attachment #558861 - Flags: review?(bhearsum)
Attachment #558861 - Flags: review?(bhearsum) → review+
Attachment #558861 - Flags: checked-in+
Flags: needs-reconfig?
Merged to production and reconfigured.
Flags: needs-reconfig? → needs-reconfig+
Flags: needs-reconfig+
This landed in production on the 9th.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Depends on: 1013493
No longer depends on: 1013493
You need to log in before you can comment on or make changes to this bug.