[Buildbot-devel] try default may confuse users

Dustin J. Mitchell dustin at v.igoro.us
Thu Apr 17 03:08:53 UTC 2014

On Wed, Apr 16, 2014 at 1:52 PM, Dan Kegel <dank at kegel.com> wrote:
> The 'buildbot try' commmand, by default, runs tests on all builders.
> In the use case where a single try scheduler is used to grant
> access to all builders, users who forget to specify which project
> they want to run a try on will find that they have spammed all
> projects with try builds of a patch from some other project.
> Might be a good idea to make "no builders" be an error that says how
> to list available builders, and add a -a option to mean "all
> builders", to avoid this surprise.

In many cases, this functionality *does* make sense: there's a single
try scheduler that is pre-configured with the appropriate set of
builders for try jobs.  So it's actually the exceptional case where
this default is inappropriate.

This will be more natural when using the force scheduler, where you
can add a scheduler for each project.

> p.s. I would have put this in trac, but it doesn't like me anymore.

Amar's working as hard as he can to build a new Trac.  It sucks, I'm
sorry.  It's nothing personal!

More information about the devel mailing list