Closed
Bug 782301
Opened 12 years ago
Closed 12 years ago
[tracker] deploy new buildbot master in mtv1
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hwine, Assigned: Callek)
References
Details
(Whiteboard: [reit] [tracker] [capacity])
+++ This bug was initially created as a clone of Bug #781743 +++
It dawns on me that with our full batch of tegras coming on line we'll want another buildbot master VM setup, to handle them.
We might be able to squeeze them all on the existing masters, but we had lots of intermittent issues clear when we split it up to the three masters from 2... and I don't want to increase the load that much again.
This bug should track relops work only, we'll get another bug on file for releng work.
I *assume* relops has all the details as to CPU's/OS/etc needed for our masters from their end.
Reporter | ||
Comment 1•12 years ago
|
||
dang, forgot to edit the comment #0 - this is the internal releng tracker for all the it & releng bugs needed to get the new buildbot master into operation.
Assignee | ||
Comment 2•12 years ago
|
||
I think all work on this is done, *but* I want to leave open until I have jobs being taken properly from this master, incase more work is needed
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → bugspam.Callek
Assignee | ||
Comment 3•12 years ago
|
||
this is, indeed now done.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•7 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•