Closed
Bug 532716
Opened 15 years ago
Closed 15 years ago
Setup 10 new win2k3 buildslaves with buildbot and get into the try server
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: joduinn, Assigned: bhearsum)
References
Details
Once the VMs are created and running in staging, we'll need to monitor them and
then move to production - shared across the pods as needed.
This bug is to track the RelEng setup work.
Assignee | ||
Comment 1•15 years ago
|
||
I'll take care of these.
Assignee: nobody → bhearsum
Summary: Setup 10 new win2k3 buildslaves with buildbot and get into production → Setup 10 new win2k3 buildslaves with buildbot and get into the try server
Comment 2•15 years ago
|
||
If we're blocked on more storage perhaps we should put some of these in the moz2 pool.
Assignee | ||
Comment 3•15 years ago
|
||
For the record, the new slaves are:
try-w32-slave20 -> try-w32-slave29
Assignee | ||
Comment 4•15 years ago
|
||
These slaves are doing a staging run right now.
Assignee | ||
Comment 5•15 years ago
|
||
Got these slaves into the production try server today.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 6•15 years ago
|
||
production ssh keys were copied in from try-linux-slave19.
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•