Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-43132

Cancel existing job if the new job is pending

    XMLWordPrintable

Details

    Description

      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

      Attachments

        Issue Links

          is related to

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-43353 Ability to abort all previous running builds

          • Major - Major loss of function.
          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-47503 Abort ongoing builds of PR if new change to the same PR was submitted

          • Major - Major loss of function.
          • Resolved
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-38409 Cancel ongoing testing of current PR if the PR gets updated with new/changed commits

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              nemanjaboric Nemanja Boric
              Votes:
              12 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: