Environment in Jenkins Pipeline has no variables

Question

Because I couldn't use an environment variable that I thought should exist, I printed all the environment variables in my Jenkins Pipeline script:

node { for(e in env) { print "key = ${e.key}, value = ${e.value}" } }

This prints:

key = null, value = null

I'm very surprised by this.

Why are there no environment variables?

maybe it's just not iterable? or just another side-effect of CPS. Try sh "set". — StephenKing
– StephenKing, Commented Feb 9, 2017 at 15:27
sh doesn't work: nohup: failed to run command "sh": No such file or directory — bsky
– bsky, Commented Feb 9, 2017 at 15:34
no.. that's not a command, it's part of the DSL. use node { sh "set" }. — StephenKing
– StephenKing, Commented Feb 9, 2017 at 16:01

Jon S · Accepted Answer · 2017-02-09 16:26:35Z

Seems to be a bug/limitation. If you look at the implementation, there is no support for iteration.

The following works as a workaround:

node { for(e in env.getEnvironment()) { print "key = ${e.key}, value = ${e.value}" } }

1 Answer 1