Jenkins does not recognize setting env variables using set -a

Question

I have a bash file that is used to set env variables. It is called setter.sh and contains something like this

set -x
var1="something"

in my jenkinsfile I do this

sh ". setter.sh"
sh "echo $var1"

However $var1 is not recognized. What could be the reasoning of this?

You can't have spaces around `=` in the assignment. – Barmar May 23 '22 at 22:06 — Barmar, May 23 '22 at 22:06
I have edited the question. My original script has no space – chickenman May 23 '22 at 22:25 — chickenman, May 23 '22 at 22:25

score 1 · Accepted Answer · answered May 24 '22 at 06:25

Your issue is not the spaces, it's the step syntax. You have two separate steps (commands) in two separate shells. sh ". setter.sh" runs in one shell and quits. The second command, sh "echo $var1" runs in a separate shell that does not know about the first's environment.

Either use a multi-line shell command or Environment Injector plugin or some other means. (warning).

Also, set -x is not relevant to the question, but set option in subject is set -a (export), body is set -x (trace).

Jenkins does not recognize setting env variables using set -a

1 Answers1