449901 - [tracking bug] Change all unittest VMs to use build cvs keys

Status: RESOLVED FIXED

Description

[Lukas Blakk [:lsblakk] use ?needinfo]

The following machines need to be updated to stgbld keys:

1.9 staging:
bm-centos5-unittest-01
bm-stage-osx-01
bm-win2k3-unittest-01
bm-vista-unittest-01 (once the license is activated and it is accessible again)

moz2 staging:

bm-centos5-unittest-02
bm-xserve-unittest-01
bm-win2k3-unittest-02-hw (when it is no longer running tracemonkey tests)

The following machines need to be updated to ffxbld keys:

(1.9 production master)

qm- centos5-01		
qm-centos5-02			
qm-centos5-04
qm-xserve01			
qm-xserve06
qm-win2k3-01			
qm-win2k3-02		
qm-win2k3-pgo01

(moz2 production master)

qm-centos5-moz2-01
qm-centos5-03
qm-centos5-moz2-02-hw
qm-moz2mini01
qm-win2k3-moz2-01
qm-win2k3-unittest-hw
qm-win2k3-03

The master.cfg for each master will need to reflect this change - so a patch should be created for:

staging-master for 1.9 and moz 2
production-master for 1.9 and moz 2

And finally all new VMs activated for unittest will use the ffxbld and stgbld keys respectively.

Comment 1

[Lukas Blakk [:lsblakk] use ?needinfo]

All the machines on 1.9 production master are using ffxbld

Comment 2

[Lukas Blakk [:lsblakk] use ?needinfo]

Now using stgbld:

1.9 staging:
bm-centos5-unittest-01
bm-stage-osx-01
bm-win2k3-unittest-01

Comment 3

[Lukas Blakk [:lsblakk] use ?needinfo]

moz2 production on production-master.b.m.o is using ffxbld and moz2 staging on staging-master.b.m.o is using stgbld.

Closing.