Status: Reopened (View Workflow)
We have set up podtemplates to facilitate the writing of jenkinsfile. Developers only have to override the values when needed. However, this inheritance relationship does not work as indicated in the doc. In fact, the values put in the jenkinsfile do not override the values in the parent podtemplate.
In the podtemplate I defined a "main" container based on an ubuntu image. In the jenkinsfile I defined a "main" container but based on a maven image. The pod was created with ubuntu and not maven. By activating the logs (org.csanchez.jenkins.plugins.kubernetes), it seems to me that the podtemplates are reversed. Because, I see in the parent the maven image and in the podtemplate the ubuntu image (see attaced log file).
This is not what is described in the doc with the maven example.
This behavior (yaml merge not overriding template being inherited from) is a new. Older versions of the plugin behaved differently.
With plugin 3724.v0920c1e0ec69, I can override values (e.g. memory limit). With plugin
3900.va_dce992317b_4 or 3923.v294a_d4250b_91, the values specified in yaml do not override the values defined in the pod template. This is with 'yamlMergeStrategy: merge()' set.
This is breaking a bunch of our pipelines.
There is no contradiction : UI fields always take precedence on what is defined by yaml.