Closed Bug 462180 Opened 16 years ago Closed 16 years ago

we need more slaves for staging-master

Categories

(Release Engineering :: General, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: armenzg, Assigned: catlee)

References

Details

We are now moving unit test to staging-master and we are trying to do l10n builds as well aside of doing periodic builds (every 2 hours), build on change, trace monkey and mobile builds with 2 slaves: moz2-linux-slave04 and moz2-win32-slave04

We need more slaves (create them or move them) and we need a bug to track other bugs (or another bug) to know which slaves are being created and added/moved to staging-master
Blocks: 460791
As per email thread:
|We currently have two slaves in staging
|moz2-linux-slave04
|moz2-win32-slave04
|
|I'd like to propose having two slaves of each o.s. in staging:
|
|moz2-linux-slave03/04
|moz2-win32-slave03/04
|moz2-darwin9-slave03/04
|
|There's a lot of work going on in staging, and we keep getting in each
|others way, so beefing up staging seems worthwhile.
|
|
|To do this, I'd like to:
|- reassign linux+win32 slave03 from production to staging...
|- leave two of the 4 new macs minis in staging once they are online.
I see the following slaves now in staging-master:
- moz2-linux-slave01
- moz2-linux-slave04
- moz2-win32-slave04
- moz2-darwin9-slave02
- moz2-darwin9-slave03
- moz2-darwin9-slave04

John, can you confirm which one of these slaves are staying and how many more windows are we adding?
Lukas, I know you set up the darwin ones (I think) are they staying or are you moving them to production at some point?
catlee and I just talked on phone. How about we consistently use moz2-*-slave03 for staging, in addition to moz2-*-slave04?
Ok, I'll move moz2-{win32,linux}-slave03 over to staging.
Assignee: nobody → catlee
Priority: -- → P2
Quick note: slave04 is turned off until we downgrade twisted - check bug 464057
Depends on: 464057
Staging now has moz2-{win32,linux,darwin9}-slave{03,04}, which will not be moving to production.
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.