Our fabulous intern Anamaria Stoica has been working hard the past few months helping to pull data from buildbot’s scheduler DB that allows us to learn all sorts of new information about how the release infrastructure is being used, and how it could be optimized. Among other things, she’s generated an end-to-end report so we can see at a glance how long the complete build cycle for any push to mozilla-central took. Now, on top of that, she’s added a way to see who is using the awesome new TryChooser syntax.
In the coming weeks I’ll be emailing folks who are using try but not the TryChooser syntax and encouraging them to give it a shot. In my stock email letter I will say something along the lines of:
When you use the TryChooser syntax to make requests for only what you need, you allow precious CPU cycle time to be used elsewhere by those who need it.
This is helpful for two reasons:
1. Those testing fixes to blockers of the next beta/rc/release can get try results quickly and get their code landed on trunk
2. Overall wait times for try results are reduced
The number of build requests is an aggregate of all the builders triggered so all build types, platforms, test and talos builders run on that push.
Now for comparison, here’s a snapshot of folks not using the TryChooser:
I have no way of knowing from this snapshot which of those pushes were intentionally not using the TryChooser and perhaps trying to get all 176 possible builds. Some of them may be using custom mozconfigs as a way to kill off unwanted builds (p.s. you get burning with that).
If you haven’t tried it yet, please give TryChooser a go and see if getting a smaller set of builds (ie: what you need, not just the default) and perhaps getting more green on you try pushes gives you a boost.