[JIRA] (JENKINS-61178) When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir

[vinc...@latombe.net (JIRA)]

Title: Message Title

Vincent Latombe created an issue   Jenkins / JENKINS-61178 When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2020-02-21 12:54 Priority: Minor Reporter: Vincent Latombe The following Jenkinsfile fails podTemplate(containers: [ containerTemplate(name: 'busybox', image: 'busybox', ttyEnabled: true, command: '/bin/cat', workingDir: '/src') ]) { node (POD_LABEL) { stage('Run') { sh 'env | sort' container('busybox') { sh 'env | sort' } } } } Whereas this one works podTemplate(containers: [ containerTemplate(name: 'jnlp', image: 'jenkinsci/jnlp-slave:latest'), containerTemplate(name: 'busybox', image: 'busybox', ttyEnabled: true, command: '/bin/cat', workingDir: '/src') ]) { node (POD_LABEL) { stage('Run') { sh 'env | sort' container('busybox') { sh 'env | sort' } } } } The reason is https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesSlave.java#L130 calls https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/PodTemplate.java#L276 which then uses the working dir of the first container defined in the pod, instead of using the jnlp container all the time. Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204721.1582289664000.4271.1582289700517%40Atlassian.JIRA.