[Buildbot-devel] Slightly better paper trail?

Bob Hood bhood2 at comcast.net
Tue Jul 28 20:41:06 UTC 2009

I'll give that a go.  Thanks, Doug!

Doug Latornell wrote:
> I think you could get the behaviour you want by reducing the value of
> the treeStableTimer when you create the Scheduler instance.  IIRC, it
> defaults to 20 minutes.  Not sure if setting it to zero would cause a
> build per commit, but it's worth a try.
> Doug
> On Tue, Jul 28, 2009 at 10:47 AM, Bob Hood <bhood2 at comcast.net
> <mailto:bhood2 at comcast.net>> wrote:
>     Might be a newb question:
>     I just discovered today that Buildbot will roll-up check-ins for a
>     build -- that is, if more than one check-in is made to the SCM
>     repository since the last build, it will check out the most
>     current, possibly pulling in other check-ins as well.
>     This kinda gives me some issues with paper trails.  The build
>     might fail as a result of any one of the check-ins that were made,
>     and I have a hard time cannot pin-pointing it (and my regression
>     builds become a bit fuzzy as well).  Is there a setting I can
>     enable (or change I can make) that will make Buildbot build
>     per-check-in so I can discretely correlate check-ins to failures?
>     I'm using Subversion as my SCM, if that's important.  And Buildbot
>     0.7.9.
>     Thanks a lot in advance.

Render me gone,                       |||
Bob                                 ^(===)^
                      "If ya can't beat 'em, tariff 'em."
                                   - /Harley-Davidson Motor Company/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20090728/f5e0e1f4/attachment.html>

More information about the devel mailing list