Could this be the same as https://issues.jenkins-ci.org/browse/JENKINS-41127 ?

This issue popped up again in the past week Is there any additional information that could help?

Currently, we are running:

• Jenkins 2.110
• Job DSL 1.69
• Pipeline 2.5

Hi even we are facing this issue , any solution for this bug will help us

Thanks

I got the same issue now and then. My DSL seed job is set concurrentBuild false.

pipelineJob(jobName)
{
    concurrentBuild(false)

...

The pipeline job configured correctly with "Do not allow concurrent builds" on, but it builds two jobs parallel.

My environment:

• Jenkins 2.60.1
• Job DSL 1.63
• Pipeline 2.5

This is an incarnation of JENKINS-31832. The many options available in the pipelineJob context are not suited for Pipeline jobs.

The correct syntax to disable concurrent builds for Pipeline jobs is

pipelineJob('example-pipeline') {
  properties {
    disableConcurrentBuilds()  
  }
}

Hi daspilker , we are using scripted pipeline DSL for all oyr projects so is there any way that we can configure this property into our projects so that we can rid of concurrent builds

Appreciate for your reply

yrsurya Ask this on the Jenkins Users Mailing List. See https://jenkins.io/mailing-lists/.

Hi, we ran into this issue after recently upgrading jenkins and the plugins (including the job dsl plugin to 1.70). As mentioned in the previous comment, following fixed it

 pipelineJob('example-pipeline') { 
 properties { 
 disableConcurrentBuilds() 
 } 
}

Just want to point out that the docs are not updated with this - https://jenkinsci.github.io/job-dsl-plugin/#path/pipelineJob-properties

Side note: I think the deprecation handling would have been safer if the seed job failed with an error instead of silently ignoring it with a warning. In this particular case, the config not getting applied silently can have a significant impact. What do you think?

First, thank you to daspilker for your hard work on job-dsl. It's deeply appreciated.

I'd second what naiquevin says above: the way this was deprecated is slightly confusing. The migration docs say the functionality is 'deprecated' and 'will be removed' in the future, and yet it appears to have been removed in 1.70 itself. We get a 'QUIET' log line from job-dsl's output, but nothing fails, and the fact that the official job-dsl docs still indicate that the old stuff should work in 1.70 is extra puzzling.

daspilker – please let us know if there's anything we can do to help remedy this. Thank you.