Closed
Bug 430899
Opened 17 years ago
Closed 17 years ago
mothball xserve16
Categories
(Release Engineering :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: joduinn, Unassigned)
References
Details
Doing housekeeping, we discovered bm-xserve16 / xserve16.
We believe this was use for Leopard testing for FF3, and is idle. We should recycle this if its no longer needed.
Nick: are you still using this or is it ok to recycle this?
| Reporter | ||
Updated•17 years ago
|
Priority: -- → P3
| Reporter | ||
Comment 1•17 years ago
|
||
Nick already confirmed in email that this machine is now idle. Is there anything on this that needs to be backedup, or can we just go ahead and reimage this machine?
Summary: mothball xserve16? → mothball xserve16
Comment 2•17 years ago
|
||
I say go ahead and re-image.
Comment 3•17 years ago
|
||
Did anyone change anything on this box ? If not, it's probably just as it was when the 10.5 image was created. I guess we should re-image just for peace of mind.
| Reporter | ||
Comment 4•17 years ago
|
||
I'm all in favour of peace of mind. Lets reimage this as a 10.5.2 build ref image, so that we can add it to the moz2 pool, along with bm-xserve17 and bm-xserve18. Filed bug#432408 for that.
Once bug#432408 is closed, I can get the buildbot slave running and connected to the moz2 pool.
Comment 5•17 years ago
|
||
This has been used for Moz2 builds for awhile.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
| Assignee | ||
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
•