Closed
Bug 554226
Opened 14 years ago
Closed 14 years ago
Mothball FF3.0 production machines
Categories
(Release Engineering :: General, defect, P4)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: joduinn, Assigned: joduinn)
References
Details
The plan is to: - ship FF3.0.19 - wait some number of days/week to make sure there is no surprise FF3.0.20 - get formal "ok to power off" from beltzner/christian/dveditz - disable nagios alerts - powerdown all remaining FF3.0.x systems - backup systems - delete VMs, recycle hardware. - remove tinderbox tree. For now, lets start by listing what machines will eventually be powered off, and make sure that nothing is missing (or also being used for something else!). According to http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox3.0, these can go: fx-linux-1.9-slave07 fx-linux-tbox fxdbug-linux-tbox bm-xserve08 bm-xserve20 fx-win32-1.9-slave07 fx-win32-tbox fxdbug-win32-tb (the inventory shows a suspiciously long list of other machines on FF3.0.x which I'll verify before adding to this bug).
Updated•14 years ago
|
Priority: -- → P4
Updated•14 years ago
|
Assignee: nobody → joduinn
Comment 1•14 years ago
|
||
3.0.x is the only thing that's keeping the old version of the l10n dashboard alive, too. So I'd mothball stuff on my side, too.
Comment 2•14 years ago
|
||
The release machines are fx-linux-1.9-slave2 fx-win32-1.9-slave2 fx-mac-1.9-slave2 (previously bm-xerve10) We also run l10n and shark nightlies on those (via buildbot). There may also be some staging slaves left over (replace 2 with 1,3,4).
Comment 3•14 years ago
|
||
Updating comment #2: fx-linux-1.9-slave2 - releases fx-win32-1.9-slave2 - releases fx-mac-1.9-slave2 - releases, 110n nightlies, shark nightlies fx-linux-1.9-slave4 - l10n nightlies fx-win32-1.9-slave4 - l10n nightlies
Assignee | ||
Comment 4•14 years ago
|
||
Notice sent to newsgroups.
Assignee | ||
Comment 5•14 years ago
|
||
Will be turning these machines off as soon as FF3.5.10 ships. Current (rescheduled) release schedule for FF3.5.10 is Tuesday, 15th June 2010.
Assignee | ||
Comment 6•14 years ago
|
||
FF3.5.10 shipped today, so its now ok to power off these FF3.0.x machines.
Assignee | ||
Comment 7•14 years ago
|
||
I've now powered off the following VMs and machines: fxdbug-linux-tbox fxdbug-win32-tbox fx-linux-1.9-slave2 fx-linux-1.9-slave04 fx-linux-1.9-slave07 fx-win32-1.9-slave2 fx-win32-1.9-slave04 fx-win32-1.9-slave07 fx-linux-tbox fx-win32-tbox production-1.9-master fx-mac-1.9-slave2 (which seems to be bm-xserve10, even though not in inventory?) bm-xserve08 bm-xserve20 We're now ready for backup and then deleting these VMs.
Comment 8•14 years ago
|
||
(In reply to comment #7) > I've now powered off the following VMs and machines: > > fxdbug-linux-tbox > fxdbug-win32-tbox > fx-linux-1.9-slave2 > fx-linux-1.9-slave04 > fx-linux-1.9-slave07 > fx-win32-1.9-slave2 > fx-win32-1.9-slave04 > fx-win32-1.9-slave07 > fx-linux-tbox > fx-win32-tbox > production-1.9-master > > > fx-mac-1.9-slave2 (which seems to be bm-xserve10, even though not in > inventory?) > bm-xserve08 > bm-xserve20 > > We're now ready for backup and then deleting these VMs. This looks like the complete list to me, FWIW.
Comment 9•14 years ago
|
||
Stopped unittest staging buildbot master at sm:/builds/buildbot/unittest-master.
Assignee | ||
Updated•14 years ago
|
Assignee | ||
Comment 10•14 years ago
|
||
Remaining work is being tracked in depbugs, so all done here.
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•