Closed
Bug 572533
Opened 14 years ago
Closed 14 years ago
setup 4 osx10.6 build slaves
Categories
(Release Engineering :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: joduinn, Assigned: bhearsum)
References
Details
(Whiteboard: [buildslaves][10.6])
Once moz2-darwin10-slave{50...54}.build.m.o are imaged by IT, this bug is to
track RelEng doing buildbot master changes.
As usual, these slaves should run in staging first, before making the move to
"live" TryServer. Once these 4 are added to production, we can move 4
pre-existing minis from production to staging, for staging use.
(I'd like to take this chance to shuffle slaves back/forth from
production/staging, so that the names line up, and its easy to tell which
machines are production, and which are staging, across the different OS.)
Reporter | ||
Comment 1•14 years ago
|
||
(In reply to comment #1)
> Once moz2-darwin10-slave{50...54}.build.m.o are imaged by IT, this bug is to
> track RelEng doing buildbot master changes.
>
> As usual, these slaves should run in staging first, before making the move to
> "live" TryServer. Once these 4 are added to production, we can move 4
> pre-existing minis from production to staging, for staging use.
>
> (I'd like to take this chance to shuffle slaves back/forth from
> production/staging, so that the names line up, and its easy to tell which
> machines are production, and which are staging, across the different OS.)
s/"live" TryServer/production/
Updated•14 years ago
|
Priority: -- → P3
Whiteboard: [buildslaves][10.6]
Comment 2•14 years ago
|
||
(In reply to comment #0)
> Once moz2-darwin10-slave{50...54}.build.m.o are imaged by IT, this bug is to
> track RelEng doing buildbot master changes.
This should read moz2-darwin10-slave{51..54}.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → bhearsum
Assignee | ||
Comment 3•14 years ago
|
||
most config work being done in bug 572524 to minimize patches.
Assignee | ||
Comment 4•14 years ago
|
||
These slaves have been moved onto pm01/pm03.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
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
•