[JIRA] (JENKINS-43177) env.WHATEVER not considered for environment variable cross reference resolution in Declarative

andrew.bayer@gmail.com (JIRA)

unread,

Mar 28, 2017, 7:58:01 PM3/28/17

to jenkinsc...@googlegroups.com

Andrew Bayer created an issue

Jenkins /

JENKINS-43177

env.WHATEVER not considered for environment variable cross reference resolution in Declarative

Issue Type:	Bug
Assignee:	Andrew Bayer
Components:	pipeline-model-definition-plugin
Created:	2017/Mar/28 11:57 PM
Priority:	Minor
Reporter:	Andrew Bayer

With an environment section like this:

 
                                                                environment {
  FOO = "something"
  BAR = "${env.FOO} else"
} 
                                                            

The EnvVars-driven environment variable resolution/expansion doesn't know that env.FOO means that it needs to resolve FOO before resolving BAR, so there's no guarantee that'll actually happen in that order, and you may well get BAR as null else.

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

andrew.bayer@gmail.com (JIRA)

unread,

Mar 28, 2017, 7:58:01 PM3/28/17

to jenkinsc...@googlegroups.com

Andrew Bayer started work on

JENKINS-43177

Change By:	Andrew Bayer
Status:	Open In Progress

Add Comment

andrew.bayer@gmail.com (JIRA)

unread,

Mar 28, 2017, 8:02:02 PM3/28/17

to jenkinsc...@googlegroups.com

Andrew Bayer commented on

JENKINS-43177

Re: env.WHATEVER not considered for environment variable cross reference resolution in Declarative

One risk of a fix I've got almost done is that it could turn

 
                                                                environment {
  FOO = "foo"
  BAR = "${env.FOO} and env.Should not change"
} 
                                                            

into BAR == "foo and Should not change" - so I'm poking around to make sure I can do that replacement solely in the curlies.