[Buildbot-devel] Hooking a new TCP-listening service into the BuildMaster

[Axel Hecht]

Maybe I'm naive, but it sounds to me like you could just add your
trigger as a change source. Shouldn't it be just that?

I know that my stuff sadly isn't, I'll need to swap a few things back
and forth to actually write my thoughts down on that. It's gonna be a
somewhat of a follow up to mails here at mozilla and Dustin's writeup.

Axel

2008/1/31, Greg Ward <gerg.ward+buildbot at gmail.com>:
> Dustin J. Mitchell wrote:
> > On Jan 31, 2008 3:14 PM, Greg Ward <gerg.ward+buildbot at gmail.com> wrote:
> >
> > I've been tossing around the idea of adding a c['extra_services']
> > variable to master_cfg.py, which the buildmaster would start at
> > application startup.  I don't have the patch handy, but it sounds like
> > your question would fit easily into that.
>
> Yeah, it sounds like I've got a good use case for that idea.  (BTW,
> shouldn't it be 'extraServices' for consistency with all the other
> config variables?)
>
> > In the interim, it's probably easiest to just set up your class as a
> > service and instantiate it directly from the BuildMaster's
> > constructor, similar to the way self.botmaster is set up.
>
> Oh.  I was hoping I could do this without patching Buildbot.  What the
> hell, I've already got 4 or 5 patches running ... what's one more?
>
>         Greg
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>