Closed Bug 435278 Opened 16 years ago Closed 16 years ago

set up additional buildslaves on 1.9 branch for doing builds and unit tests on the same buildslaves

Categories

(Release Engineering :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lsblakk, Assigned: lsblakk)

References

Details

This is the tracking bug for setting up 2 * linux and 2 * win2k3 buildslaves on 1.9 in order to try and track what needs to be set up for them to be able to perform unittests and try to determine if they could then be assigned either build or unittest as needed.
Depends on: 435280
Depends on: 435289
Depends on: 435291
No longer depends on: 435289
Depends on: 435292
No longer depends on: 435280
Priority: -- → P3
Summary: set up additional buildslaves on 1.9 branch to test for doing builds and unit tests on the same buildslaves → set up additional buildslaves on 1.9 branch for doing builds and unit tests on the same buildslaves
Assignee: nobody → lukasblakk
This might turn into setting up steps on master.cfg for the existing slaves to start running unittests on available slaves.  More details to come.
Lukas, what is the bug that says from which machines were these cloned?
From the linux kernel version we don't really think they were cloned from staging or production slaves in 1.9
If you follow the dependent bugs, you should get to the creation of VMs bug.

All our VMs are imaged from the CentOS5-ref-tools-vm for future reference.
Depends on: 446038
We have set up 

fx-linux-1.9-slave07
fx-linux-1.9-slave08
fx-linux-1.9-slave09

fx-win32-1.9-slave07
fx-win32-1.9-slave08
fx-win32-1.9-slave09

bm-xserve20
bm-xserve21

These could feasibly be used as build machines if needed, but for now they will be doing unittests on production-master.b.m.o:2005
Status: NEW → RESOLVED
Closed: 16 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.