-
Bug
-
Resolution: Fixed
-
Major
-
jenkins 2.47
kubernetes-plugin 0.11
Before version 0.11
We were able to declare in the global jenkins configuration a PodTemplate with containers.
Here an simple pipeline example that was working with a global PodTemplate with 0.10
stage("Example"){ node("mypod"){ container("golang"){ sh ''' echo "something" ''' } } }
With 0.11 we get an error:
org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class org.csanchez.jenkins.plugins.kubernetes.pipeline.PodTemplateStep is missing
It is now (with 0.11) mandatory to have the PodTemplate and containers declare within the pipeline to be able to make the «container» step work again.
[JENKINS-42315] PodTemplate is now mandatory within pipeline
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
Comment |
[ I also encountered this problem, and follow this operation {code:java} // Using 0.11, global PodTemplate named "mypod": podTemplate(name: "mypod") { node("mypod") { stage("Build") { container("code-builder") { // build steps elided } } } }{code} result like {code:java} // code placeholder [Pipeline] podTemplate [Pipeline] // podTemplate [Pipeline] End of Pipeline ERROR: Cloud does not exist: kubernetes Finished: FAILURE {code} I use kubernetes plugin 0.11, when can you upgrade kubernets plugins? ] |
I am seeing this issue too, with globally configured PodTemplates. As a workaround, I have modified my pipelines like this:
With the upgrade to 0.11, add a podTemplate declaration to the top, referencing the global PodTemplate:
It's unfortunate that 0.11 introduces a breaking API change.