| The bug (with pull request which resolves it) has been posted some time ago in the old repo issue page: https://github.com/nemccarthy/stash-pullrequest-builder-plugin/issues/121 Issue description by jordijansen: Hi, I'm having a issue using the "Cancel outdated jobs" option. I'm having two job definitions that built the same repository (so they get triggered on the same Pull Requests, however they do two completly different things). When I have the option "Cancel outdated jobs" activated it will also cancel the jobs of the other job definition. For example:
Lets say I have have jobs A and B. I create a PullRequest, Job A is added to the queue. A little while later Job B is added to the queue because it triggers on the same repository/pull request. Job B cancels Job A because the Cancel outdated jobs option is activated. I think it should only cancel the Jobs that are of the same definition (Job A may only cancel jobs of Job A type). |
