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

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title

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) -- 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. For more options, visit https://groups.google.com/d/optout.