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

RESOLVED FIXED

Status

Release Engineering
General
P2
normal
RESOLVED FIXED
7 years ago
4 years ago

People

(Reporter: armenzg, Assigned: armenzg)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Comment hidden (empty)
(Assignee)

Comment 1

7 years ago
Half to production and half to the try server.
(Assignee)

Updated

7 years ago
Duplicate of this bug: 561435
(Assignee)

Updated

7 years ago
Priority: -- → P4
(Assignee)

Comment 3

7 years ago
Nothing to be done until bug 647287 is fixed.
Assignee: armenzg → nobody

Updated

7 years ago
Blocks: 667024
(Assignee)

Comment 4

7 years ago
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
Assignee: nobody → armenzg
Priority: P4 → P2
I don't like win64 as a distro - 64 is a bitlength, not a version number.  I'd rather use w2k8.
Er, I meant 'win2k8', sorry.
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.
(Assignee)

Updated

7 years ago
Summary: setup slaves w64-ix-slave[12-31].b.m.o after cloning → setup slaves w64-ix-slave{10,12,17,19-24}.b.m.o after cloning
(Assignee)

Comment 8

7 years ago
This initial set is setup and in production.
Nothing left to be done.
Status: NEW → RESOLVED
Last Resolved: 7 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.