Closed Bug 643551 Opened 14 years ago Closed 14 years ago

Allocate build slaves for preproduction release master

Categories

(Release Engineering :: General, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 650224

People

(Reporter: rail, Assigned: rail)

References

Details

(Whiteboard: [preproduction][buildslaves])

Pre-production release master needs at least 1 slave per platform: linux linux64 macosx macosx64 win32 Slave config should be documented.
Is this "allocated" as in with slavealloc, or "allocated" as in the slaves need a particular configuration that will make them unsuitable for other purposes? Actually, we could do both - add a new 'purpose' to the slave allocator, named 'preprod', and then put the slaves with that purpose in the 'preprod' pool, too.
(In reply to comment #1) > Is this "allocated" as in with slavealloc, or "allocated" as in the slaves need > a particular configuration that will make them unsuitable for other purposes? IIRC, I need to: 1. replace ssh keys with preproduction keys 2. point buildbot.tac to preproduction release master 3. remove allocated slaves from production pool (production_config.py) > Actually, we could do both - add a new 'purpose' to the slave allocator, named > 'preprod', and then put the slaves with that purpose in the 'preprod' pool, > too. I'm not familiar with slavealloc yet. If you could help me, I'm in! :)
OK, that's a far less drastic change than I thought, so it should be fine. I'll take care of the slavealloc config when we get there.
Should be fixed by 650224
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.