Closed
Bug 475748
Opened 15 years ago
Closed 15 years ago
more VMs for moz2-master staging and try server
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
References
Details
Attachments
(4 files, 1 obsolete file)
5.55 KB,
patch
|
catlee
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
2.26 KB,
patch
|
mozilla
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
313 bytes,
patch
|
Details | Diff | Splinter Review | |
3.83 KB,
patch
|
catlee
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Updated•15 years ago
|
Priority: -- → P3
Assignee | ||
Comment 1•15 years ago
|
||
1 more of each platform for staging-master, 1 more of each platform for production try, 1 of each platform for staging try.
Summary: more VMs for moz2-master staging → more VMs for moz2-master staging and try server
Assignee | ||
Updated•15 years ago
|
Priority: P3 → P2
Assignee | ||
Comment 2•15 years ago
|
||
Note that two of each are going to move to the try server after they get some testing in this environment.
Attachment #359831 -
Flags: review?(catlee)
Updated•15 years ago
|
Attachment #359831 -
Flags: review?(catlee) → review+
Assignee | ||
Comment 3•15 years ago
|
||
Comment on attachment 359831 [details] [diff] [review] add new slaves to staging changeset: 712:cfddb5fa30ac
Attachment #359831 -
Flags: checked‑in+ checked‑in+
Assignee | ||
Comment 4•15 years ago
|
||
I've got these new slaves attached to staging moz2-master now and will let them run over the weekend. If all goes well I will move 1 of each platform to staging/production try next week.
Assignee | ||
Comment 5•15 years ago
|
||
This patch puts the burden on BuildSlaves.py to provide lists of slaves per platform. This should make it easier in the future to add new slaves, as we don't need to patch any checked-in files - and we'll only have one place that lists the slaves. I'll attach what BuildSlaves.py looks like now, too.
Attachment #360322 -
Flags: review?(aki)
Assignee | ||
Comment 6•15 years ago
|
||
This isn't getting checked in, just for reference.
Comment 7•15 years ago
|
||
Comment on attachment 360322 [details] [diff] [review] add new slaves to tryserver This looks good for try, since the setup is relatively simple. If we ever approach staging or production's level of complexity we should revisit.
Attachment #360322 -
Flags: review?(aki) → review+
Assignee | ||
Comment 8•15 years ago
|
||
Comment on attachment 360322 [details] [diff] [review] add new slaves to tryserver Checking in master.cfg; /cvsroot/mozilla/tools/buildbot-configs/tryserver/master.cfg,v <-- master.cfg new revision: 1.22; previous revision: 1.21 done
Attachment #360322 -
Flags: checked‑in+ checked‑in+
Assignee | ||
Comment 9•15 years ago
|
||
Alright, try-{win32,linux}-slave04 are on the production try master, and the slave05 ones are on staging. The only thing left to do here is the Macs, after bug 475747 is done.
Assignee | ||
Comment 10•15 years ago
|
||
Attachment #360554 -
Flags: review?(catlee)
Assignee | ||
Comment 11•15 years ago
|
||
Attachment #360555 -
Flags: review?(catlee)
Assignee | ||
Updated•15 years ago
|
Attachment #360554 -
Attachment is obsolete: true
Attachment #360554 -
Flags: review?(catlee)
Updated•15 years ago
|
Attachment #360555 -
Flags: review?(catlee) → review+
Assignee | ||
Comment 12•15 years ago
|
||
Comment on attachment 360555 [details] [diff] [review] the right patch changeset: 724:311914621fb7
Attachment #360555 -
Flags: checked‑in+ checked‑in+
Assignee | ||
Comment 13•15 years ago
|
||
The new try slaves are in production + staging, I'll be hooking up the new staging-master slave tomorrow. Almost done here.
Assignee | ||
Comment 14•15 years ago
|
||
moz2-darwin9-slave08 is now attached to staging-master's moz2-master instance. We're all done here.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•