[Buildbot-devel] master status

Nick Trout nick at rockstarvancouver.com
Mon Jul 11 20:17:51 UTC 2005


> On Behalf Of Kreinick, Michael H.
> >But it's actually quite useful for developing debugging
> >configs as well.
> You can reload your config using buildbot sighup (or kill), and you
can
> force changes with buildbot sendchange. Maybe not under Windows, I
guess.

I'm not aware of an equivalent in Windows NT. A search of the MS site
reveals:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnucmg/
html/UCMGch09.asp

Okay this command line functionality is useful to discover. I missed
some of this when diving into Buildbot. The learning curve is fairly
steep if you start dabbling with Twisted as well.

> wxPython isn't any easier than installing GTK, then pyGTK. Obviously
this
> doesn't apply if, like you, you have wxPython installed already,
but...

We could install both but I'd rather stick with one. As I say I think
wxPython is more portable than PyGTK which makes BB more portable. I
only asked if Brian would consider wxPython. I think the client that
Brain suggests would be of limited use to us anyway. The waterfall
supplies most of the useful information we need. Probably Tk is the best
solution because it is the default GUI.

> Getting back to the original point, could you explain what exactly
you're
> trying to accomplish, just for my curiosity's sake? Originally I
thought
> you
> were planning on writing an IDE plugin. Now it seems like you want to
> write
> an IM notification layer, but not build off the existing Words status
> target. But I don't understand why you need queries (rather than just
> events) if you're doing an IM notification.

You're along the right lines. I want a service that listens to, and
broadcasts messages, to interested clients. I'd like several different
streams of information and I'm looking to reuse components of Twisted
and Buildbot where possible.

> Lastly, I agree that bb could use some sort of wiki, but there may not
be
> the critical mass of users yet to make it really useful. For the
moment,
> making the documentation available on the front page, no matter how
> unpolished or even flat-out wrong at times, and then fixing it, seems
to
> me a more valuable approach.

What's a critical mass? Do you really need 20-30 people? I guess we have
different approaches. I think having an editable site where people could
comment where things are wrong or where they could ask for clarification
on something would be more useful. The admins of the site would act as
editors and could contribute when time allowed. 

Nick







More information about the devel mailing list