[Buildbot-devel] Possible to change buildbot's change selection logic?

Dustin J. Mitchell dustin at v.igoro.us
Sun Oct 26 20:40:05 UTC 2014

Actually, I think the merging you're seeing is coming from
mergeRequests -- the schedulers are queueing up multiple
buildrequests, one for each push, but the builders are helpfully
building only the most recent.  You can disable that by setting


On Fri, Oct 24, 2014 at 8:47 AM, Charles Lepple <clepple at gmail.com> wrote:
> On Oct 24, 2014, at 8:26 AM, Aran Deltac <bluefeet at gmail.com> wrote:
> What I'd like, for the staging builder, is for it to not build the first
> change separate from the rest.  I want it to wait for all the changes to be
> recognized and test them all together.  As it stands right now, whenever
> anyone pushes a project to the stg branch, the builder is going to run two
> builds before the developer gets what they wanted and that'll take 30
> minutes or more rather than the 15 or so minutes that a single build would
> take.
> It sounds like you need the treeStableTimer setting:
> http://docs.buildbot.net/current/manual/cfg-schedulers.html#singlebranchscheduler
> To set the timer, look at twistd.log to see how quickly your change source
> sends changes to Buildbot (I assume it's a "push" setup, rather than a
> poller). Then, make sure your timer is large enough to handle variations in
> that time span. This delays the start of the build, but hopefully less than
> the fifteen minutes it would take to run an extra build.
> --
> Charles Lepple
> clepple at gmail
> ------------------------------------------------------------------------------
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel

More information about the devel mailing list