[JENKINS-43353] Option to disable concurrent builds by aborting previous ones

[jglick]

JENKINS-43353, more straightforward and efficient than using the previous hack

def buildNumber = BUILD_NUMBER as int; if (buildNumber > 1) milestone(buildNumber - 1); milestone(buildNumber)

Can be configured via GUI (for standalone Pipelines) or as code

properties([disableConcurrentBuilds(abortPrevious: true)])

[jglick]

Some other usages that could be cleaned up:

• https://github.com/jenkinsci/jenkins/blob/677fbb2a81fa8e9a0bc37ad5eca56565612e1f2e/Jenkinsfile#L8
• https://github.com/jenkinsci/bom/blob/c0d113b152a688f729b52c8551c131b2585348bb/Jenkinsfile#L1
• https://github.com/jenkinsci/plugin-compat-tester/blob/230b64415f1f2500dfd233e983911614f1dd2f3e/Jenkinsfile#L5
• https://github.com/jenkinsci/kubernetes-plugin/blob/d844788b8e186e587ac9cad200ff2dbf3feacc06/Jenkinsfile#L1

[jglick]

@cathychan & @jtnord point out that when introducing this option for the first time, say to replace the milestone trick, you leave one extra build of an existing job running because the property is only interpreted when starting a build, not when the property is added (for example via properties step in Jenkinsfile). Probably DisableConcurrentBuildsJobProperty could be improved to override setOwner to immediately abort any running build(s) other than the latest.