Closed Bug 485821 Opened 16 years ago Closed 15 years ago

Make SeaMonkey buildbots use one generic pool per platform

Categories

(SeaMonkey :: Release Engineering, defect)

Product:
SeaMonkey
Component:
Release Engineering
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: kairo, Assigned: kairo)

References

Details

Currently, SeaMonkey has one-machine pools for build and test machines, we should move to one generic pool per platform for all of build and test on all branches.
Depends on: 492222
Depends on: 492224
Depends on: 493448
Depends on: 493449
Depends on: 493450
Blocks: 492224
No longer depends on: 492224
Blocks: CcMcBuildIssues
Blocks: 494676
I'm right now working on the transition of the new pooled setup to production, and just have encountered bug 502031 that currently stops us to get the old unit test VMs into the new slave pools.
Depends on: 502031
The pools are up on production, but I can't join the old VMs to the pools, so leaving open until bug 502031 is solved.
Blocks: 504344
The pooled setup works in production now with all VMs we have, the ones missing are due to bug 493321 right now (cb-seamonkey-linux-02 and cb-seamonkey-osx-04 are what we're leaving turned off for the moment due to that).
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Assignee: nobody → kairo
Component: Project Organization → Release Engineering
QA Contact: organization → release
You need to log in before you can comment on or make changes to this bug.