By default, builds on Aurora are (still) non-unified. Running non-unified builds on top of that adds no value and is a needless utilization of build resources.
Created attachment 8372933 [details] [diff] [review] only run non-unified builds on trunk I fixed up the static analysis block below it to exclude more recent b2g branches.
Assignee: nobody → ryanvm
Status: NEW → ASSIGNED
Attachment #8372933 - Flags: review?(catlee)
Created attachment 8372934 [details] [diff] [review] only run non-unified builds on trunk Merged try into it too. Please verify that I've got the logic correct here.
Comment on attachment 8372934 [details] [diff] [review] only run non-unified builds on trunk https://hg.mozilla.org/build/buildbot-configs/rev/dbad1fc22333
Attachment #8372934 - Flags: checked-in+
Comment on attachment 8372934 [details] [diff] [review] only run non-unified builds on trunk And a bustage fix: https://hg.mozilla.org/build/buildbot-configs/rev/b942de49c482
Live in production (not getting CCed).
Looks like it worked. Non-unified builds just started on trunk trees as expected and not on Aurora/Try.
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.