When updating a PodTemplate (specifically a containerTemplate) through a jenkinsfile change, the change is not immediately put into effect.

This seems to be some kind of caching issue, in older versions you could see this through the "Configure System" which would have the old template still populated. Is it especially apparent when someone is on a branch improving the build , but "old" template builds are still happening on master with the same label. In this situation it seems a bit of a race condition as to which version is picked up in the job.

Workaround;
We have resorted to changing the template label to force a cache bust. e.i
label: 'GitPod1' ... label: 'GitPod2' etc. which works reliably.

P.S Finally getting around to recording some bugs that I have known about for a while, sorry for the spam