-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Jenkins 2.77
kubernetes plugin 1.0
- In /configure, I have a "default" podTemplate defined.
- I have a job that uses declarative syntax. When it runs, it evidently creates an ephemeral podTemplate with the same name as its label.
- While that job is running, if I open /configure, this ephemeral podTemplate shows up in the list. Then I make an unrelated change and hit the Save button.
- Once the build finishes, I can open /configure again and the formerly ephemeral podTemplate for that specific job is still there.
- If I change the config in the Jenkinsfile for that job, I think the persistent podTemplate silently overrides it.
- duplicates
-
JENKINS-49166 Pod Templates declared in pipeline have side-effect to the kubernetes cloud configuration
- Resolved
- relates to
-
JENKINS-49200 Dynamic podTemplate not available when resuming pipeline after restart
- Resolved