[Buildbot-devel] Various BuildBot questions

Fred L. Drake, Jr. fdrake at acm.org
Thu Sep 16 04:00:41 UTC 2004

On Friday 10 September 2004 03:23 pm, Brian Warner wrote:
 > Actually editing html.py will leave the IRC 'force build' command enabled.
 > You'd have to disable that separately, by commenting out command_FORCE in
 > buildbot/status/words.py .

Right; it doesn't look too hard to provide an option at constructor time.

 > In CVS, both kinds of 'force build' are currently broken, becuase the
 > IStatus object that html.py and words.py use is "read only". I plan to add
 > a new IControl interface (or something) which will bring that
 > functionality back. In doing that, my vague plan is to add an
 > allowForceBuild= flag to both Waterfall() and IRC() that will
 > enable/disable those routines I suggested you comment out.

I started looking at the CVS version tonight, and modified 
buildbot.status.html such that Waterfall takes an allow_force Boolean flag 
that enables/disables the force feature.  It wasn't hard.

Changing the patch to support different values for enable_force should be easy 
enough, but the specific values should probably be documented in the 

 > From there, we can probably expand on the idea with
 > allowForceBuild='admin' to indicate that force-build is allowed but only
 > when some kind of admin password is required.

Yes, that would be cool, and useful to boot.  ;-)

 >  updating step_twisted.py to the current interfaces
 >  generalizing step_twisted.Trial, making it useful for all Trial-using
 > trees figure out 0.5.0-compatibility stuff, old-slave/new-master stuff
 > bring back force-build
 >  lots of testing

When I tried to bring up the master with my modified sources (with a slave 
runninnng the same code), it looks like the HTML interface always shows the 
slave as being offline.  The log on the master indicates the slave attached 
and slaveinfo was received, but the user interface indicates "offline".  The 
log on the slave doesn't have any errors either.

 >  new HTML display (no history, just current/last-build status per builder)
 >  IRC "noisy": tell the buildbot to announce whenever a build passes/fails,
 >   ask it to watch a given build

Very cool!


Fred L. Drake, Jr.  <fdrake at acm.org>

More information about the devel mailing list