Major JENKINS 1.544 ignores env var JENKINS_HOME for the WAR extraction.
D:\temp>set JENKINS_HOME=D:\temp\jserver
D:\temp>java -jar jenkins-1.531.war
Running from: D:\temp\jenkins-1.531.war
webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")
18.12.2013 10:13:21 winstone.Logger logInternal
INFO: Beginning extraction from war file
=> extracts to D:\temp\jserver\war
D:\temp>set JENKINS_HOME=D:\temp\jserver
D:\temp>java -jar jenkins-1.544.war
Running from: D:\temp\jenkins-1.544.war
webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")
18.12.2013 10:15:15 org.eclipse.jetty.util.log.JavaUtilLog info
INFO: jetty-8.y.z-SNAPSHOT
18.12.2013 10:15:17 org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Extract jar:file:/D:/temp/jenkins-1.544.war!/ to C:\Documents and Settings\...\Local Settings\Temp\jetty-0.0.0.0-8080-jenkins-1.544.war-any\webapp
=> extracts to C:\Documents and Settings\...\Local Settings\Temp\jetty-0.0.0.0-8080-jenkins-1.544.war-any\webapp, why?
- duplicates
-
JENKINS-20682 Starting Jenkins with defined --webroot or JETTY_HOME not working.
-
- Resolved
-
- is related to
-
-
- Resolved
-
Caused by the move to Jetty in 1.535.
Note that the extraction location was never defined to be within JENKINS_HOME to the best of my knowledge, so while it was changed, it doesn't look like a regression unless you define --webroot.
There are numerous solutions related to how Jetty determines the directory to extract to, many mentioned in
JENKINS-20682. So I'm resolving this as duplicate of that issue.