Open Bug 746208 Opened 8 years ago Updated Last year
[Tracking Bug] Setup a TBPL/treeherder service for Sea
(In reply to Dustin J. Mitchell [:dustin] from bug 698843 comment #1) > From what I understand, the plan is to complete this work before April 30, > when we'll need to move out of sjc1 and leave the momo infrastructure behind. (In reply to Justin Wood (:Callek) from bug 698843 comment #10) > (In reply to Serge Gautherie (:sgautherie) from comment #9) > > Fwiw, what is the plan wrt SeaMonkey, which uses (at least) > > http://build.mozillamessaging.com/tinderboxpushlog/?tree=SeaMonkey > > We might (likely) need to reinstall tbpl on our own infra to support > SeaMonkey -- That lies with me. (In reply to Mark Banner (:standard8) from bug 745952 comment #3) > (In reply to Serge Gautherie (:sgautherie) from comment #2) > > Fwiw, would something like this work for SeaMonkey too? (If yes, how should > > we proceed?) > > No, it won't, the FF tbpl is hooked into the buildbot api closely and that > is not available to the community machines. Thunderbird can do this because > Thunderbird is moving to the same build system as FF. Workaround: Use legacy http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey
PS: In other words, we should try to "reuse"/recreate what MozMess had done until now.
Nothing in this depends on bug 745952. Bug 698843 and the move of hardware is really your issue. The easiest thing to get you up and running would be to clone http://hg.mozilla.org/users/gozer_mozillamessaging.com/tinderboxpushlog/ and use that as a base. It is quite old, but was before all the client/server & build api integration stuff. If you then update to the build API things, you can probably update your clone to the latest version.
No longer depends on: 745952
A nit, while here: Add SeaMonkey-Release branch.
http://build.mozillamessaging.com/tinderboxpushlog/ returns "build.mozillamessaging.com could not be found." now :-< It was fine yesterday. (Ftr, probably related to bug 755391.)
(In reply to Serge Gautherie (:sgautherie) from comment #4) > (Ftr, probably related to bug 755391.) Could be "related", but not the same cause. Do you know what happened?
Severity: major → critical
I have a temporary instance up at: http://tbpl.drapostles.org/ it is my private server, and I'll hope to get it somewhere better soonish. I did not do much of any Config tweaks (so far only tweak was to make SeaMonkey the default shown tree), and had to fight a bit to get the log parsing working. TBPLBot does not work (yet). Given that we have /something/ useable up, I'm dropping severity.
Severity: critical → normal
(In reply to Justin Wood (:Callek) from comment #6) > I did not do much of any Config tweaks (so far only tweak was to make > SeaMonkey the default shown tree), and had to fight a bit to get the log > parsing working. Could you comment out Thunderbird* entries (which are available at tbpl.m.o)? And add SeaMonkey-Release?
Summary: Investigate continuing TBPL service for SeaMonkey → [Tracking Bug] Setup a TBPL/treeherder service for SeaMonkey
You need to log in before you can comment on or make changes to this bug.