Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: kubernetes-plugin
-
Labels:None
-
Similar Issues:
Description
In our pipelines we use pod templates to specify the build environment. The issue is that when I update a container image in the pod template the old version of the pod template still exists on Jenkins. This is evident in the "Cloud" settings within Jenkins /configure page. A new template is also created with the correct settings. However an issue arises because the pod label is the same on both templates and Jenkins uses the old template.
I consider this a bug because I feel that whatever is specified in my pod template code should be what is run.
One possible solution on my end is to version the name of the pod template and I believe that would alleviate these issues. However without any sort of proper cleanup the amount of templates will just build and build within the Jenkins configure page which is certainly undesirable.
Ideally I feel that nothing should be stored on Jenkins in terms of pod templates and only my pod template code upon execution is considered.
Thoughts?
Thanks for your time.
Attachments
Issue Links
- duplicates
-
JENKINS-47759 Updating podTemplate does not immediately come into effect.
-
- Resolved
-
Thanks for the link Lars. Seems to be a duplicate issue.
The plugin seems to be cleaning up the pod templates on Jenkins itself (which it wasn't previously doing). Not sure if this was from a Jenkins / plugin update but that is great.
Reading the other issue we seem to agree the way to go is to version the label name to mitigate any issues.
I'll close issue. Thanks.