Closed Bug 466855 Opened 16 years ago Closed 16 years ago

Replace old try slaves

Categories

(Release Engineering :: General, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mozilla, Assigned: mozilla)

References

Details

Attachments

(1 file)

Create new try server slaves: try-linux-slave01 try-linux-slave02 try-win32-slave01 try-win32-slave02 Afterwards, retire: sm-try1-linux-slave sm-try2-linux-slave sm-try1-win32-slave sm-try2-win32-slave
Depends on: 466862
Depends on: 466863
rm -rf mozilla is timing out for windows on prod try server.
Attachment #351628 - Flags: review?(nthomas)
Comment on attachment 351628 [details] [diff] [review] increase windows clobber timeout Checking in master.cfg; /cvsroot/mozilla/tools/buildbot-configs/tryserver/master.cfg,v <-- master.cfg new revision: 1.21; previous revision: 1.20 done
Attachment #351628 - Flags: review?(nthomas) → review+
Attachment #351628 - Flags: checked‑in+
Ok, try server is running all new slaves. (the original mac is on try-staging) We just need to mothball the old boxes now; do we want to keep them around, or just nuke? I don't have VI access currently if we want to nuke 'em...
There's nothing of value on the old slaves - I'll delete them.
Alright, they've been deleted.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: