-
Bug
-
Resolution: Fixed
-
Major
-
None
Unlike documented here https://github.com/jenkinsci/pipeline-model-definition-plugin/wiki/Syntax-Reference such sample doesn't work
environment { FOO = "bar" OTHER = "${FOO}baz" }
Firstly ${FOO} cannot work it is a groovy variable and it should be escaped
OTHER = "\${FOO}baz"
or
OTHER = '${FOO}baz'
And even by escaping it it's not working
and we have
[declarative-pipeline] Running shell script + printenv ... OTHER=nullbaz ... FOO=bar ...
note that FOO is seen as null which makes no sense in shell env (it should be empty if unknown.
cc abayerjglickrsandell (should it be considered as a bug ? Or an improvement to do ?)
- is duplicated by
-
JENKINS-42666 wrong environment configuration in the syntax reference wiki page
- Closed
-
JENKINS-41386 need to support or reject non string based environment variables.
- Closed
-
JENKINS-41623 Variable Expansion in Global Variables Not Occurring
- Closed
-
JENKINS-41890 Declarative syntax: ${env.WORKSPACE} not set in environment block
- Closed
- links to