-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins ver. 2.43, EZ Templates v1.2.5
I've a String Parameter with Default Value provided in the template. I've also existing job using that template. Once the default value has been changed in the template, it doesn't reflect the changes in the job which using that template. Re-saving job doesn't help either. As for workaround only removing that parameter from the job, then it's recreated correctly. I believe the same problem happens with Choice Parameter on changes in the template.
Unfortunately, this is a feature not a bug. I shall add a page to the main wiki on "how it works" to avoid confusion. EZ isn't like a version control system. It doesn't know the original state before a change - just that template and child are different and it must make some static decision on which value to choose. Its main usecase is a job property being different from the template. When template's default and child's default differ, EZ assumes that the child has specialised itself (child wins).
I'll re-title this and leave it open as an Enhancement because I think it represents a sensible desire for EZ to work like other inheritance systems