647287 - setup slaves w64-ix-slave{10,12,17,19-24}.b.m.o after cloning

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Comment 1

[Armen [:armenzg]]

Half to production and half to the try server.

Comment 3

[Armen [:armenzg]]

Nothing to be done until bug 647287 is fixed.

Comment 4

[Armen [:armenzg]]

We now have slaves to start putting into staging:
w64-ix-slave20
w64-ix-slave21
w64-ix-slave22
w64-ix-slave23
w64-ix-slave24

First thing is to add them to slavealloc and to figure out why we are having a D drive rather than an E drive.

dustin what do you think of the following import file.
I have chosen "win64" as the distro name; do you prefer another name? The other values seem to have been using in other pools.
name,basedir,distro,bitlength,purpose,datacenter,trustlevel,speed,environment,pool
w64-ix-slave20,e:\builds\moz2_slave,win64,64,build,scl1,dev,ix,dev/pp,staging-pers

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

I don't like win64 as a distro - 64 is a bitlength, not a version number.  I'd rather use w2k8.

Comment 6

[Dustin J. Mitchell [:dustin] (he/him)]

Er, I meant 'win2k8', sorry.

Comment 7

[Matthew Larrain[:MaRu]]

Adding 4 more for staging/prod

w64-ix-slave10
w64-ix-slave12
w64-ix-slave17
w64-ix-slave19

We figured out the D/E drive issue by resolving it with a VBS script.

Comment 8

[Armen [:armenzg]]

This initial set is setup and in production.
Nothing left to be done.