[Tracking bug] Shut down old tryserver & send it's slaves to be re-imaged/re-purposed

RESOLVED FIXED

Status

Release Engineering
General
P3
normal
RESOLVED FIXED
8 years ago
5 years ago

People

(Reporter: lsblakk, Assigned: joduinn)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [shutdown][revisit this bug by July 12, 2010])

Doing this will mean no more CVS tryserver - so double check/announce that well.
(Reporter)

Comment 1

8 years ago
More detail on what this entails:

* Maemo builds on sm-try-master need to be over in try-as-branch first (bug 561439)
* try-linux-slave{02,03} brought over to build network, re-imaged, put into the try builder pool
* delete sm-try-master and sm-staging-try-master
I've shut down the old rev2 talos master at talos-master.m.o:8011; bug 568268 already recycled the qm-p${platform} slaves. The staging talos talos-staging-master is nearly dead in bug 557267.
This master is no longer needed.  I am going to turn the master process off but leave the infrastructure in place and running until at least July 12, 2010.

-sm-try-master.mozilla.org
-try-linux-slave02
-try-linux-slave03
Whiteboard: [shutdown][revisit this bug by July 12, 2010]
(Reporter)

Updated

8 years ago
Depends on: 577711
(Reporter)

Comment 4

8 years ago
I'm filing bugs to take the two linux slaves out of the sandbox and get them into our try builder pool.  We can power off the master on the 12th.
(Reporter)

Comment 5

8 years ago
passing this to John O'Duinn to power off, backup, then delete sm-try-master.mozilla.org

Once that is done, this bug can be closed.
Assignee: lsblakk → joduinn
Status: NEW → ASSIGNED
Filed dep.bug to have IT take backup.
I think this bug can be closed, based on the dependents being finished and the whiteboard comment. John?
(In reply to comment #7)
> I think this bug can be closed, based on the dependents being finished and the
> whiteboard comment. John?

Found during triage. 100% correct, bhearsum. FIXED!!
Status: ASSIGNED → RESOLVED
Last Resolved: 8 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.