983731 - Drop the lastgood requirement for nightlies off m-c

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Jason Smith [:jsmith]]

In order to ensure we're running the latest m-c bits for daily smoketesting, an offline discussion has proposed that we switch to generating m-c nightly builds every three hours.

Comment 1

[[e-mail] (:bhearsum)]

The e-mail thread made me think that it wasn't the frequency that was the issue, but the time. What if we moved the current periodic times by 3h? Eg, if we're building at 6pm now, build at 9pm instead.

Comment 2

[Ryan VanderMeulen [:RyanVM]]

Attachment: change m-c to 1hr

I think the frequency is an issue as well, because that directly affects the max interval between a push and "all clear" for nightly purposes. With a 6 hour interval, you're looking at up to ~10hr for that (6hr if you just missed the last periodic run + ~4hr for all builds to run). If we drop the interval to 1hr, that gets us to a ~5hr interval which is certainly better.

As discussed on IRC, I don't think per-push is needed since landings on m-c tend to be in spurts (i.e. sheriffs merging the 3 integration branches over a short period of time). But this will at least make sure that the last merge cset always gets a periodic run shortly after.

Comment 3

[Ryan VanderMeulen [:RyanVM]]

Attachment: disable lastgood on m-c and change the periodic interval to 3hr

Per IRC discussion, lastgood doesn't really do what it claims on m-c, so let's just drop it. Also, set the periodic interval to 3hr to match the trunk integration branches.

Comment 4

[Ryan VanderMeulen [:RyanVM]]

Comment on attachment 8391337 [details] [diff] [review]
disable lastgood on m-c and change the periodic interval to 3hr

https://hg.mozilla.org/build/buildbot-configs/rev/4263564033b3

Comment 6

[Justin Wood (:Callek)]

In production