Closed Bug 843356 Opened 7 years ago Closed 7 years ago

[Tracking bug] remove SeaMonkey dependency on tinderbox.m.o

Categories

(SeaMonkey :: Release Engineering, defect)

x86
macOS
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Unassigned)

References

Details

from quick meeting w/callek, it seems most work is done, and the highlights of remaining work are:

* use treestatus to open/close SeaMonkey tree
* setup buildbot queue db, instead of the current db inside SeaMonkey buildbot master
** this needs a VM? and a db server?
* setup buildapi server, using the queue db
** this needs a VM

Please link any dep bugs you file as you go.
Depends on: 845635
(In reply to John O'Duinn [:joduinn] from comment #0)
> * setup buildbot queue db, instead of the current db inside SeaMonkey
> buildbot master
> ** this needs a VM? and a db server?

This does not need its own VM, SeaMonkey prefers not to manage our own MySQL server, and previously :sheeri gave us a verbal ok for MoCo making sense to handle this for us. I just had deprioritized getting that request formal until now.

Said DB creation+access is now tracked in Bug 845635 (marked moco-conf due to the details I listed in its c#0 and potential data that will get shared there)

---

A bit burnt today from other work, so will get the rest of the tree-of-bugs filed tomorrow.
Depends on: 845844
Depends on: 848222
sooo, I have http://tbpl-dev.callek.net/ now, I'm working out the last few kinks there, and a few outstanding needs with IT/opsec around this buildout. but I can officially and publicly call Tinderbox no longer blocked on SeaMonkey.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
(In reply to Justin Wood (:Callek) from comment #2)
> sooo, I have http://tbpl-dev.callek.net/ now, I'm working out the last few
> kinks there, and a few outstanding needs with IT/opsec around this buildout.
> but I can officially and publicly call Tinderbox no longer blocked on
> SeaMonkey.

V.cool. Thanks Callek!
You need to log in before you can comment on or make changes to this bug.