Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
Description
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.
One risk of a fix I've got almost done is that it could turn
into BAR == "foo and Should not change" - so I'm poking around to make sure I can do that replacement solely in the curlies.