Say I have one open PR:
that triggered a build “Check-PR” #1 which is currently running.
I think I observed that if in the meanwhile I open a second PR “branch2 > master”, the rolling build feature will abort #1 and trigger a “Check-PR” build #2. Eventhough the 2 PRs do not originate from the same branch (branch1!= branch2).
Then again, while #2 is still running if I push on branch. It triggers a third build #3 that aborts #2.
Instead, for me expected behaviour would be :
- Opening the PR “branch2 > master” does not abord currently running builds regarding PR “branch1 > master” similarly pushing on branch2 does not abort currently running builds regarding PR “branch1 > master”
- Pushing on branch1 while a build regarding PR “branch1 > master” is running abort that last build and starts a new build (but do not abort build regarding PR “branch2 > master”)
In short “rolling build” should abort older running builds having the exact same couple “branchToBeMerged/targetedBranch” not just having the same “targetedBranch”.
Is that clear ? Is that the same feature that is requested by @j.kaan in the current thread ?