tag:help.appveyor.com,2012-11-13:/discussions/problems/3555-rolling-builds-not-very-usefulAppVeyor: Discussion 2018-10-19T08:17:35Ztag:help.appveyor.com,2012-11-13:Comment/384501322015-11-12T23:02:21Z2015-11-12T23:02:21ZRolling builds not very useful<div><p>OK, do you have a suggestion on how to improve them?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/384501322015-11-12T23:45:47Z2015-11-12T23:45:47ZRolling builds not very useful<div><p>Add an option to do basically the same thing but keeping one
build per branch (treating a PR on github as a different
branch)</p>
<p>This would save us a few builds, not a lot, but anything that
helps...</p></div>travistag:help.appveyor.com,2012-11-13:Comment/384501322015-11-13T04:54:37Z2015-11-13T04:54:37ZRolling builds not very useful<div><p>Well, looking at the implementation of rolling builds... this is
actually how they are supposed to work. If you start a new
<code>master</code> build all other "master" builds will be
cancelled; if you start a new "some_other_branch" build all other
"some_other_branch" builds will be cancelled, but not "master"
ones. The same for PRs, but PR # is the key there. Do you observe a
different behavior?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/384501322017-09-23T12:22:50Z2017-09-23T12:22:50ZRolling builds not very useful<div><p>I think the rolling builds do work as Feodor explained.</p></div>mloskottag:help.appveyor.com,2012-11-13:Comment/384501322017-09-23T13:25:04Z2017-09-23T13:25:04ZRolling builds not very useful<div><p>The rolling builds work also for pull requests.</p>
<p>So, I think there is no issue any more.</p></div>mloskot