Thanks for reporting this issue. We have been able to reproduce it and this should not be happening. It seems that after doing an
export, Jenkins is showing this line:
As a (recommended) workaround, you should create a wrapper script at a known location to get it working. For example, in
And then you would add the following command in Jenkins (please note that it should be the first command always):
After that command, you could, for example, add
echo $HOME so the resulting command to be executed would be something like:
. /home/tomcat/builds/setenv.sh; echo $HOME;
I will create a case for further investigation on our side.
Hope it helps!