On 2012-04-07 21:39, Sami Tikka wrote:
There is nothing special in how Jenkins gets the value of the PATH
environment variable: It inherits PATH from its parent process. What
the parent process is and why it sets PATH to the value you see,
depends on how you start Jenkins.
If you have used one o
There is nothing special in how Jenkins gets the value of the PATH
environment variable: It inherits PATH from its parent process. What
the parent process is and why it sets PATH to the value you see,
depends on how you start Jenkins.
If you have used one of the "native installers" available at
je
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
