On 01/10/12 10:51 PM, Justin Lebar wrote:
For case 1., an idea that has been floated here and again (in Automation and
Tools and Release Engineering, anyway) is landing directly from try ->
inbound (or central) for green try pushes. However, this isn't a small
endeavor, both for the reasons of building the infra + software to do this
as well as the fact that since the average random oranges/push is high
landing is such a manual process. If this is something we want, though, we
should ticket it and estimate what this will really take.
A very simple way to approximate this would be the following policy:
* If you have a recent green try build, you can land on inbound with
DONTBUILD.
I think this would likely result in even more headaches for sheriffs
and is optimizing for load on the wrong tree (m-i is only 25% of our
load, while try is 50%), but it would be easy to try out, so maybe we
should do it for a day or two and see if the result is chaos.
That's just the load in terms of # of pushes. Load in terms of % time
spent on the various branches is pretty different. For the past 30 days,
here's the breakdown of time of builds and tests spent on the top 4
branches:
39.93% mozilla-inbound
31.00% try
6.91% mozilla-central
6.22% mozilla-aurora
Actual machine load from try is disproportionally lower than its share
of pushes would indicate. I would guess this is due to not running the
full set of builds/tests via try syntax, or from cancelling jobs early.
It's also interesting because jobs on try never coalesce, whereas this
happens quite a bit on mozilla-inbound.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
