[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

vincent@latombe.net (JIRA)

unread,

Feb 21, 2020, 7:55:03 AM2/21/20

to jenkinsc...@googlegroups.com

Vincent Latombe assigned an issue to Vincent Latombe

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

Change By:	Vincent Latombe
Assignee:	Vincent Latombe

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

vincent@latombe.net (JIRA)

unread,

Feb 21, 2020, 7:55:03 AM2/21/20

to jenkinsc...@googlegroups.com

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'
            }
        }
    }
}
 
                                                            