[Buildbot-devel] Trigger specific buildbot slaves using svn_watcher.py

Charles Lepple clepple at gmail.com
Sun Jun 20 14:53:45 UTC 2010

On Jun 20, 2010, at 10:44 AM, Nick Bolton wrote:

> On 20 June 2010 15:33, Bob Hood <bhood2 at comcast.net> wrote:
>> Have you considered at the "fileIsImportant" Scheduler option?  You  
>> can
>> trigger builds based upon your own defined logic using it.
> Hmm, yes, this might be what I'm looking for. Thanks. I will try and
> figure out how to fit this in to our master.cfg

I was actually just thinking about that when I saw Bob's email.

If you don't look at the list of changes for a build in the web  
status, then fileIsImportant will solve the problem of building too  
frequently, and you're done.

On the other hand, if you want to see what commits contributed to a  
failed build, then fileIsImportant will add a while bunch of trunk  
commits to your release build status pages.

I'm not sure when the change_filter parameter got added, but if you  
can't pass in the branch information (as explained in my other email),  
then that might be something to look at instead:


More information about the devel mailing list