Jean-Paul Calderone wrote:

I guess the config for this particular behavior would look something like...

You were right that I needed two schedulers for that. Unfortunately, it doesn't work at all, because svn_buildbot.py does not report branches on which a change happened, so if you have multiple schedulers for a subversion source, they either all build when a change occurs, or none of them. If svn_version knew about branches (which I'll have to implement, or incorporate the patch that I saw somewhere), it would probably work - I have now code to create builders and schedulers in a nested loop.

Builds can also be forced using the IRC bot, and there may be a commandline tool for doing this as well. I doubt there's any authentication required when using the IRC bot, so it doesn't really help restrict forcing to commits only.

Currently, my buildbot isn't connected to IRC at all. If I ever enable that aspect, I'll use allowForce=False again to disable remotely invoking builds.

Another possibility might be to place the form (or just the form action) behind HTTP auth. I'm not sure if this is feasible with the authentication mechanism used to restrict access to the svn repository.

Not easily, no. We don't have passwords from the committers, and authentication through SSH keys is not supported in the Web. If people really need to be able to force a build, I can activate that, of course - but not with explicit consent of the operators of the build slaves. Regards, Martin