Closed
Bug 1536559
Opened 6 years ago
Closed 6 years ago
Run Mac builds in GCP at tier 3
Categories
(Taskcluster :: Workers, enhancement)
Taskcluster
Workers
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla68
People
(Reporter: coop, Assigned: grenade)
References
Details
Attachments
(1 file)
+++ This bug was initially created as a clone of Bug #1525094 +++
We've already run Mac builds in GCE (they run on the same instances as Linux, see https://bugzilla.mozilla.org/show_bug.cgi?id=1529951#c23), but we should enable them at tier 3 as well.
Assignee | ||
Comment 1•6 years ago
|
||
this change adds support for parallel gcp builds for the following macosx build configurations:
- macosx64
- debug
- opt
- shippable/opt
implementation notes:
- this patch mostly mirrors the equivalent windows-on-gcp patch at: https://phabricator.services.mozilla.com/D24865
- gcp builds are triggered with a treeherder tier 3 flag so that they are only displayed in the treeherder ui when the user has a tier 3 flag set.
- gcp builds use a th build symbol of "Bg" to make them easy to differentiate from ec2 builds in the treeherder ui.
- gcp builds use a perfherder "gcp" flag to make them easier to differentiate from ec2 builds in the perfherder ui.
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → rthijssen
Status: NEW → ASSIGNED
Assignee | ||
Updated•6 years ago
|
Attachment #9056681 -
Flags: review?(pmoore)
Comment 2•6 years ago
|
||
Comment on attachment 9056681 [details]
run macosx64 builds in gcp at tier 3
Looks fine (apart from the points raised by wcosta). Thanks!
Attachment #9056681 -
Flags: review?(pmoore) → review+
Assignee | ||
Comment 3•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Keywords: checkin-needed
Pushed by ncsoregi@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a1127948b460
run macosx64 builds in gcp at tier 3 r=pmoore,wcosta
Keywords: checkin-needed
Comment 5•6 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in
before you can comment on or make changes to this bug.
Description
•