650736 - Find a way for SeaMonkey to utilize the pending/running/etc. reports from MozillaMessaging (for tbpl)

Status: RESOLVED WONTFIX

(SeaMonkey :: Release Engineering, defect)

Description

[Justin Wood (:Callek)]

Gozer, John.

Is there a way for SeaMonkey to feed data into the MoMo pending/running/etc. database, such that we can also get that type of feedback on tbpl, and/or utilize a self-serve install you might one-day setup?

I imagine it is *possible* I just don't know enough about the system/setup involved.

Comment 1

[John Hopkins (:jhopkins)]

Deferring to gozer as he set up the pending/running/etc service.

Comment 2

[Justin Wood (:Callek)]

Gozer, ping?

Comment 3

[John Hopkins (:jhopkins)]

Justin: have you looked at buildapi?  Here is our fork, customized to work for our production buildbot instance:

https://hg.mozilla.org/users/gozer_mozillamessaging.com/buildapi-thunderbird

Comment 4

[Justin Wood (:Callek)]

(In reply to John Hopkins (:jhopkins) from comment #3)
> Justin: have you looked at buildapi?  Here is our fork, customized to work
> for our production buildbot instance:
> 
> https://hg.mozilla.org/users/gozer_mozillamessaging.com/buildapi-thunderbird

Given our (SeaMonkey) current lack of hardware to use for _anything_ I was hoping there was a way that we could *share* the infra you have...

Beyond that the software support should be quite simple by comparison.

Comment 5

[Philippe M. Chiasson (:gozer)]

(In reply to Justin Wood (:Callek) from comment #0)
> Gozer, John.
> 
> Is there a way for SeaMonkey to feed data into the MoMo pending/running/etc.
> database, such that we can also get that type of feedback on tbpl, and/or
> utilize a self-serve install you might one-day setup?

Injecting data in the database isn't really possible, without a lot of hassle. The way this works right now is that buildapi looks into the buildbot master's mysql database for this info and exposes it as a json dump that tbpl loads.

Including seamonkey data without sharing buildbot infrastructure would be very hard.

> I imagine it is *possible* I just don't know enough about the system/setup
> involved.

The solution, actually, would be to teach tbpl to be able to aggregate information from multiple sources, instead of assuming a single authoritative source.

This would fix this problem, and also make it possible for all of us to run a single instance of tbbl, for example.

Comment 6

[Robert Kaiser]

(In reply to Philippe M. Chiasson (:gozer) from comment #5)
> The way this works right now is that buildapi looks into the
> buildbot master's mysql database for this info and exposes it as a json dump
> that tbpl loads.

I somewhat feared that was the case. SeaMonkey's buildbot currently runs on sqlite because I couldn't figure out how to set it up with mysql as a backend (even if I knew we might want it in the future for things like that).

Comment 7

[Justin Wood (:Callek)]

MoMo tbpl/buildapi no longer exists, so its either going to be a "figure out how to share Firefox infra" (unlikely here) or "get our own up"