-
New Feature
-
Resolution: Duplicate
-
Major
Pushing the code and triggering new job will not abort the previous one, making the user wait for the results of the previous job before the new one is performed. It would be nice if there was an option to abort the existing job and immediately start running the new one.
Here's the similar issue reported against github-organization-folder-plugin: https://issues.jenkins-ci.org/browse/JENKINS-38409
Here's the issue in the old Github Pull request builder plugin where it was implemented: https://github.com/jenkinsci/ghprb-plugin/issues/241
- is related to
-
JENKINS-43353 Ability to abort all previous running builds
- Resolved
-
JENKINS-47503 Abort ongoing builds of PR if new change to the same PR was submitted
- Resolved
- relates to
-
JENKINS-38409 Cancel ongoing testing of current PR if the PR gets updated with new/changed commits
- Resolved