Disable non-unified builds on Aurora

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
4 years ago
19 days ago

People

(Reporter: RyanVM, Assigned: RyanVM)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [capacity])

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

4 years ago
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

4 years ago
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)
(Assignee)

Comment 2

4 years ago
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.
Attachment #8372933 - Attachment is obsolete: true
Attachment #8372933 - Flags: review?(catlee)
Attachment #8372934 - Flags: review?(catlee)

Updated

4 years ago
Attachment #8372934 - Flags: review?(catlee) → review+
(Assignee)

Comment 4

4 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
Live in production (not getting CCed).
(Assignee)

Comment 6

4 years ago
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
(Assignee)

Updated

4 years ago
See Also: → bug 1043091
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.