Jobs created from SEED job no longer getting updated

[Substance586]

I've been happily using this plugin for a few months but have just run into a major roadblock.  For some reason I have lost the ability for any of my SEED jobs to update existing jobs, despite not changing anything in the SEED jobs and not checking the 'Ignore changes' box in the DSL build step config.  

It doesn't matter if it's an existing SEED job or a new one.  My only resort is to delete the existing jobs and recreate them from scratch, but this only works once as the newly-generated jobs do have the most recent config but then they also won't get updated the next time the SEED job runs.  There's nothing in the logs to suggest anything wrong and even upgrading to the 1.39 version of job-dsl doesn't fix the problem or give a clue that there is a problem.  I believe this started occurring after my company's most recent Jenkins upgrade (from 1.580.x to 1.609.1).  I've updated most of my core Jenkins plugins beyond just the job-dsl but nothing seems to help. 

Just wondering if anyone here has seen behavior like this before or can provide some advice on how to proceed with debugging this problem?

[Substance586]

I should have also added that the generated jobs still show that are being built by the SEED job and vice-versa.

Here's an except of my Seed job's console log:

Processing DSL script MyDeploymentPipeline.groovy
Existing items:
    GeneratedJob{name='app_stageToEnvA'}
    GeneratedJob{name='app_verifyOnEnvA'}
    GeneratedJob{name='app_smokeTestOnEnvA'}
    GeneratedJob{name='app_activateOnEnvA'}
    GeneratedJob{name='app_stageToEnvB'}
    GeneratedJob{name='app_verifyStageOnEnvB'}
 ... etc. ...
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Notifying upstream projects of job completion
Finished: SUCCESS

[Substance586]

I came across an error when I was trying to revert to a previous job configuration and a quick google search led me to this, which appeared to be my problem in a nutshell:

https://issues.jenkins-ci.org/browse/JENKINS-27548

The workaround presented at the end of the thread is working for me and, while hardly an ideal solution, at least keeps this plugin a viable option for me until a long-term fix can be put into effect. 

[Daniel Spilker]

Thanks for the info. I wasn't aware of that issue.

I create a JIRA filter containing all open Job DSL bugs (component job-dsl-plugin) and all bug reports related to the Job DSL plugin (labeled job-dsl). This should make it easier to find this kind of issue: https://issues.jenkins-ci.org/issues/?filter=15140

And I added the link to the wiki:
https://github.com/jenkinsci/job-dsl-plugin/commit/e895deded46bc00918147851eedc3c80d19007d1

Daniel

--
You received this message because you are subscribed to the Google Groups "job-dsl-plugin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to job-dsl-plugi...@googlegroups.com.
To post to this group, send email to job-dsl...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/job-dsl-plugin/b5de8edb-0166-4b58-9f54-cdee7c15283e%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Substance586]

I appreciate the updates Daniel.  And I may be mistaken and this problem no longer exists in newer versions of Jenkins, I just have no easy way of verifying that.