-
Bug
-
Resolution: Duplicate
-
Minor
-
Debian 8.6
Jenkins 2.19.4
Parameters dissappeared when configured (after upgrade of jenkins? Not sure anyway).
Upon accessing the job and entering the configuration of the job and unmarking "This project is parameterized" and saving I get the following in the jenkins log:
Dec 15, 2016 3:02:44 PM com.joelj.jenkins.eztemplates.exclusion.JobParametersExclusion merge
INFO: +++ new parameter [RELEASE]
Dec 15, 2016 3:02:44 PM com.joelj.jenkins.eztemplates.exclusion.JobParametersExclusion merge
INFO: +++ new parameter [SPIN]
Dec 15, 2016 3:02:44 PM com.joelj.jenkins.eztemplates.exclusion.JobParametersExclusion merge
INFO: +++ new parameter [PROJECT]
Dec 15, 2016 3:02:44 PM com.joelj.jenkins.eztemplates.exclusion.JobParametersExclusion merge
INFO: +++ new parameter [SUFFIX]
Dec 15, 2016 3:02:44 PM com.joelj.jenkins.eztemplates.exclusion.JobParametersExclusion merge
INFO: +++ new parameter [KEEP_WS]
Dec 15, 2016 3:07:59 PM hudson.plugi
After this the parameterized build works just fine again.
It seems like the data is still available but just needs to be resynced.
Any advice on how to resync all the data for eztemplates would also be nice as I currently have 100+ jobs for which I have to go through the gui to enable the parameters again.
1 Install a backup solution so this never happens again. (I used ThinBackup jenkins plugin).
2 Make sure you have latest build (1.2.5 at this moment) of ez-templates.
3 Generally saving a config change to the template will resync every single impl (can take quite some time for 100s of jobs)
4 If that doesn't and you find must manually resave impl projects then Jenkins has a pretty robust REST API. You can GET the config file for a job then POST it straight back to mimic a dummy save. See first two curl commands here:
https://benkiew.wordpress.com/2012/01/12/automating-hudsonjenkins-via-rest-and-curl-a-very-small-cookbook/
Let me know ho it goes!