[JIRA] (JENKINS-57939) Nested PodTemplate erroneous behaviour

7 views

Skip to first unread message

cwebb@thoughtworks.com (JIRA)

unread,

Jun 10, 2019, 10:23:02 AM6/10/19

to jenkinsc...@googlegroups.com

Christopher Webb created an issue

Jenkins /

JENKINS-57939

Nested PodTemplate erroneous behaviour

Issue Type:	Bug
Assignee:	Carlos Sanchez
Components:	kubernetes-plugin
Created:	2019-06-10 14:22
Priority:	Minor
Reporter:	Christopher Webb

See the following:

 
                                                                podTemplate(label: 'x', inheritFrom: 'JenkinsDeployer', nodeUsageMode: 'EXCLUSIVE') {
    node('x') {
        echo env.environment
        podTemplate(label: 'y', inheritFrom: 'JenkinsLiveDeployer', nodeUsageMode: 'EXCLUSIVE') {
            node('y') {
                echo env.environment
            }
        }
    }
} 
                                                            

Right now, assuming environment on each pod template are respectively pre-production and and production, the actual result of the code snippet above is:

 
                                                                // node starting
'pre-production'

// node starting
'pre-production'

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

cwebb@thoughtworks.com (JIRA)

unread,

Jun 10, 2019, 10:25:02 AM6/10/19

to jenkinsc...@googlegroups.com

Christopher Webb updated an issue

Jenkins /

JENKINS-57939

Nested PodTemplate erroneous behaviour

Change By:	Christopher Webb

See the following:

{code:java}

podTemplate(label: 'x', inheritFrom: 'JenkinsDeployer', nodeUsageMode: 'EXCLUSIVE') {
    node('x') {
        echo env.environment
        podTemplate(label: 'y', inheritFrom: 'JenkinsLiveDeployer', nodeUsageMode: 'EXCLUSIVE') {
            node('y') {
                echo env.environment
            }
        }
    }

}{code}

Assuming there are pod templates for a 'JenkinsDeployer' which have a set of environment variables and then a pod template for 'JenkinsLiveDeployer', which has a different set of environment variables, then I would expect to see a different value for each echo statement.

Right now, assuming environment on each pod template are respectively pre-production and and production, the actual result of the code snippet above is:

{code:java}

// node starting
'pre-production'

// node starting
'pre-production'

{code}

whereas the expected value should be:
{code:java}

// node starting
'pre-production'

// node starting

'production'
{code}

This should be the same behaviour as doing:

{code:java}
node('label') {
  echo env.environment
  node('live-label') {
    echo env.environment
  }
}{code}