$WORKSPACE/../../../..
[jenkins@builder01-slave01 ~]$ echo $JENKINS_HOME
/opt/jenkins
Maybe the Jenkins process was started as "root" and not as the "jenkins" user, and they've defined $JENKINS_HOME for the wrong user?
Yes, that is the expected behavior. JENKINS_HOME only matters on Jenkins master. JENKINS_HOME is the path where all metadata of Jenkins instance like plugins, jobs are stored. It is not a variable for slave.
Are you the Jenkins admin such that you have administration permission on the Jenkins UI?
Why don’t you define an environment variable with different name in the Manage Jenkins -> Configure System. This env variable is then available to all jobs regardless where the job is running.
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/502de496-603d-4c3f-935a-a723c0821e6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.