• Type: New Feature
• Resolution: Duplicate
• Priority: Major
• Component/s: github-branch-source-plugin, workflow-multibranch-plugin
• Labels:

  • multi-branch

[JENKINS-43132] Cancel existing job if the new job is pending

Nemanja Boric created issue - 2017-03-27 15:52

Nemanja Boric made changes - 2017-03-27 16:07

Description

Original: If `disableConcurrentBuilds` is enabled for a job, 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.

New: If `disableConcurrentBuilds` is enabled for a job, 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

Nemanja Boric made changes - 2017-03-27 16:13

Description

Original: If `disableConcurrentBuilds` is enabled for a job, 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

New: 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

Nemanja Boric made changes - 2017-03-27 16:14

Component/s		New: github-branch-source-plugin [ 20858 ]
Component/s	Original: workflow-job-plugin [ 21716 ]

Nemanja Boric made changes - 2017-03-27 16:15

Description

Original: 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

New: 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

Leandro Lucarella made changes - 2017-07-19 13:30

Priority

Original: Minor [ 4 ]

New: Major [ 3 ]

R. Tyler Croy made changes - 2018-03-01 19:29

Link

New: This issue relates to JENKINS-38409 [ JENKINS-38409 ]

Nicholas Brown made changes - 2018-03-16 11:52

Link

New: This issue is related to JENKINS-47503 [ JENKINS-47503 ]

Nicholas Brown made changes - 2019-03-14 11:37

Component/s

New: workflow-multibranch-plugin [ 21465 ]

Nicholas Brown made changes - 2019-03-14 11:37

Labels

New: multi-branch

Nicholas Brown made changes - 2019-03-14 11:46

Link

New: This issue is related to JENKINS-43353 [ JENKINS-43353 ]

Load more newer history items