Klaus Schniedergers added a comment - 2018-09-10 21:23 When looking into the config.xml, it seems that it's still `<concurrentBuild>false</concurrentBuild>` - so what should the replacement be for the supposedly-deprecated `concurrentBuild(false)` in pipeline jobs?

Klaus Schniedergers added a comment - 2018-09-10 21:33 Workaround: pipelineJob( 'jobname' ) { configure { (it / 'concurrentBuild' ).setValue( ' false ' ) }

Grigor Lechev added a comment - 2018-11-05 09:54 I believe this is the new correct way to do it: pipelineJob( "name" ) { properties { disableConcurrentBuilds() } ...

Klaus Schniedergers added a comment - 2018-11-05 18:48 Thanks, that seems to work, mooncrosser .

Ilguiz Latypov added a comment - 2020-06-22 21:08 - edited I would expect that concurrentBuild()s still be allowed by default, but my keeping the "Do not allow" checkbox clear and allowing the multiple node selection in a parameter still generates a single run. The concurrent runs should be allowed/controlled outside our pipeline script even when the latter limits itself to that parameter in a chain "has to run on the node parameter JENKINS_PARAM_RUN_NODE node" -> "fetch the Jenkinsfile script from SCM" -> "execute the script" -> "start the DSL pipeline on a label specified again in DSL via the node parameter JENKINS_PARAM_RUN_NODE". ========== SCM Jenkinsfile ===================== LIBRARY_PIPELINE( [ jenkinsJobInitialAgent: env.JENKINS_PARAM_RUN_NODE ?: 'windows' , ... ] ) ========== the library's vars/LIBRARY_PIPELINE.groovy =========== def call(Map configuration) { pipeline { agent { label configuration.jenkinsJobInitialAgent } ... } }