<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On May 15, 2017, at 12:29 PM, Chris Spencer wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">It should also cancel a running build for a branch if there's a newer commit pending.</span></div></blockquote></div><br class=""><div class="">I don't think that automatically cancelling a build once it starts has ever been part of the base scheduler classes (at least, in 0.8). You might be able to do this by hitting the web status interface from another scheduler, though it might make sense to have a heuristic for allowing a build to run to completion if it is nearly done anyway.</div><div class=""><br class=""></div><div class="">The collapse options are for queued builds (modulo the 0.9.x bug that Pierre mentioned), and the treeStableTimer can be used to wait for several commits to arrive, in order to give them a chance to be collapsed.</div><div class=""><br class=""></div></body></html>