Closed
Bug 967337
Opened 12 years ago
Closed 12 years ago
Disable non-unified builds on Aurora
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: RyanVM, Assigned: RyanVM)
References
Details
(Whiteboard: [capacity])
Attachments
(1 file, 1 obsolete file)
|
2.04 KB,
patch
|
catlee
:
review+
RyanVM
:
checked-in+
|
Details | Diff | Splinter Review |
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.
| Assignee | ||
Comment 1•12 years ago
|
||
I fixed up the static analysis block below it to exclude more recent b2g branches.
| Assignee | ||
Comment 2•12 years ago
|
||
Merged try into it too. Please verify that I've got the logic correct here.
Attachment #8372933 -
Attachment is obsolete: true
Attachment #8372933 -
Flags: review?(catlee)
Attachment #8372934 -
Flags: review?(catlee)
Updated•12 years ago
|
Attachment #8372934 -
Flags: review?(catlee) → review+
| Assignee | ||
Comment 3•12 years ago
|
||
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+
| Assignee | ||
Comment 4•12 years ago
|
||
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
Comment 5•12 years ago
|
||
Live in production (not getting CCed).
| Assignee | ||
Comment 6•12 years ago
|
||
Looks like it worked. Non-unified builds just started on trunk trees as expected and not on Aurora/Try.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•