Closed
Bug 564058
Opened 15 years ago
Closed 14 years ago
Move try slaves out of sandbox and into build network
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: lsblakk, Assigned: jabba)
References
Details
Please move try-w32-slave20 (10.2.76.173) out of the sandbox and into the build network.
Reporter | ||
Comment 1•15 years ago
|
||
Also move try-linux-slave08 and try-mac-slave13 into build.
OS: Windows Server 2003 → All
Summary: Move try-w32-slave20 into build network → Move try slaves out of sandbox and into build network
Reporter | ||
Updated•15 years ago
|
Severity: normal → major
Updated•15 years ago
|
Assignee: server-ops → jdow
Flags: colo-trip+
Comment 2•15 years ago
|
||
is there any else that needs to be done other than updating dns and moving the ports over to the buld vlan?
Reporter | ||
Comment 3•15 years ago
|
||
actually, yes. in fact these will need to be re-imaged with their respective ref-images since they are in the sandbox and not guaranteed to be safe. we should start with clean images in the build network.
Reporter | ||
Comment 4•15 years ago
|
||
Eta on this?
Comment 5•15 years ago
|
||
try-win32-slave20 and try-linux-slave08 are both VMs. Can I delete these now?
Reporter | ||
Comment 6•14 years ago
|
||
delete them and recreate them again with the same names, but in the build network? - yes
Comment 7•14 years ago
|
||
try-w32-slave20.build.m.o 10.2.90.170
try-linux-slave08.build.m.o 10.2.90.171
Assignee | ||
Comment 8•14 years ago
|
||
try-mac-slave13.build.m.o 10.2.90.173
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•