753172 - make sure release masters always have darwin10 machines

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[hwine]

with the sjc1 shutdown, needed to snag some of the few remaining darwin10 boxen for the new beta release master (bm13).

This bug captures that, as I did it by locking the build master - after the release, they should be unlocked

Slave                   distro          was on          now on
moz2-darwin10-slave44	darwin10	bm08-build1	bm13-build1
moz2-darwin10-slave46	darwin10	bm26-build1	bm13-build1
moz2-darwin10-slave49	darwin10	bm07-build1	bm13-build1
moz2-darwin10-slave53	darwin10	bm26-build1	bm13-build1
moz2-darwin10-slave55	darwin10	bm08-build1	bm13-build1

Comment 1

[hwine]

(none of these slaves were currently building, did graceful shutdown, then rebooted)

Comment 2

[[e-mail] (:bhearsum)]

We need a better long term way to do this. Migrating around slaves with every release in unacceptably hand-on. We should probably just put all of the moz2-darwin10 machines in the build-scl1 pool.

Comment 3

[Chris AtLee [:catlee]]

(In reply to Ben Hearsum [:bhearsum] from comment #2)
> We need a better long term way to do this. Migrating around slaves with
> every release in unacceptably hand-on. We should probably just put all of
> the moz2-darwin10 machines in the build-scl1 pool.

WFM

Comment 4

[Chris Cooper [:coop] (he/him)]

(In reply to Chris AtLee [:catlee] from comment #3)
> (In reply to Ben Hearsum [:bhearsum] from comment #2)
> > We need a better long term way to do this. Migrating around slaves with
> > every release in unacceptably hand-on. We should probably just put all of
> > the moz2-darwin10 machines in the build-scl1 pool.
> 
> WFM

Done.

Anything else to do here?

Comment 5

[hwine]

Per IRC chat, nothing else to do. Thanks, coop!