Closed Bug 422298 Opened 18 years ago Closed 17 years ago

mothball old (and unused now) 1.8 Firefox nightly build machines

Categories

(Release Engineering :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Assigned: joduinn)

References

Details

In bug#417147, we migrated nightly build production to the release automation machines. We are no longer using: * pacifica-vm * prometheus-vm * bm-xserve02 ...to produce nightly builds, and can now mothball these machines.
Summary made me blink a couple of times, so just clarifying it.
Summary: mothball 1.8 Firefox nightly build machines → mothball old (and unused now) 1.8 Firefox nightly build machines
Assignee: nobody → joduinn
Priority: -- → P2
prometheus-vm is still being used for generating nightly updates. Will make sure nothing else running on it, but not to mothball this machine for now.
I think we can go ahead and delete pacifica-vm. Do you think we can just transfer nightly updates to production-pacifica-vm?
(In reply to comment #3) > I think we can go ahead and delete pacifica-vm. Do you think we can just > transfer nightly updates to production-pacifica-vm? > pacifica-vm is a win32 box, it just does builds and nothing else. Safe to remove I think. prometheus-vm only does nightly updates now. It seems like it'd be better to have nightly updates not live on a build machine. Could it live on the AUS server?
Sorry, should have noticed this much earlier, but bm-xserve02 is currently building * Tb 2.0.0.x nightlies for en-US and locales * Fx 2.0.0.x nightlies for locales so repurposing it is blocked on the l10n project and automating Thunderbird.
Leaving bm-xserve02 and prometheus-vm running until the other build processes are removed. Pacifica-vm powered off and can be deleted after it is backed up (in bug#427832).
Priority: P2 → P3
(In reply to comment #6) > Leaving bm-xserve02 and prometheus-vm running until the other build processes > are removed. > > Pacifica-vm powered off and can be deleted after it is backed up (in > bug#427832). Deleted pacifica-vm. R.I.P.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
If Mark is referring to this bug it is still an active bug. Or do I have install the nightly build?
(In reply to comment #8) Did you mean to comment on another bug ?
Turns out to be some harmless confusion of attachment and bug id's.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.