When I execute a job containing the followin shell script
echo PATH=$PATH
on master and on a slave I get different outcomes.
== Job executed on master: ==
PATH=/sbin:/usr/sbin:/bin:/usr/bin
PATH when logging in with ssh as jenkins user:
/usr/lib64/ccache:/usr/local/bin:/bin:/usr/bin:/usr/sbin:/sbin:/var/lib/jenkins/bin
== Job executed on slave: ==
PATH=/usr/kerberos/bin:/usr/lib64/ccache/bin:/usr/local/bin:/bin:/usr/bin
Path when logged in as jenkins user:
/usr/kerberos/bin:/usr/lib64/ccache/bin:/usr/local/bin:/bin:/usr/bin:/home/jenkins/bin
In neither case are the PATHs from the ssh shell and the jenkins job the
same, but on master it is particularly reduced. I want
/usr/lib64/ccache/bin to be in the PATH on master, and I would like to
understand how jenkins gets the value it uses for PATH.
I have EnvInject plugin installed and I'm running jenkins 1.458.
Thanks,
Thomas
