[Buildbot-devel] Various BuildBot questions

[Brian Warner]

>  > 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
>  > interfaces.
> 
> I haven't heard any interest on this.  Brian, if you're interested in my 
> patch, I'll be glad to pass it along.  If you have any more ideas about how 
> this should work for 0.6.0, I might be able to find a little time to look at 
> it again later tonight.

Yes, I'd appreciate the patch. Let's say allow_force=False means never,
allow_force=True means always, and set aside the following values to do cool
things in the future:

 "admin": allow the buildmaster admin to start a build (requires some
          password-checking logic, and of course we need to define the cred
          backend stuff in the config file somehow)
 "bob": allow a user (someone who can commit to the project's source tree)
        named Bob to start a build. This will require per-user passwords
        or something.
 ["alice", "bob"]: allow these users to start builds


I think these values will be useable by the IRC status bot too. You can't
have a user named "admin", but I don't think that's a big deal.

thanks,
 -Brian