-
Bug
-
Resolution: Fixed
-
Major
In Winstone 0.9.x we used to explode war under $JENKINS_HOME/war. When we moved to Jetty-based Winstone 2.0, this code was gone and now Jetty explodes war in /tmp/jetty-0.0.0.0-8080-jenkins.war-any.
This tends to be problematic because various distros periodically clean up files under /tmp based on their modification dates. When exploded war files disappear from under us, all sorts of strange errors happen.
We should resurrect the old behaviour and explode the war file under $JENKINS_HOME.
- is duplicated by
-
JENKINS-21018 After upgrading from v1.529 to any version later that v1.542 and then updating any plugin, jenkins becomes unsusable.
-
- Resolved
-
-
JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity
-
- Resolved
-
-
JENKINS-20858 Images missing from Jenkins UI
-
- Closed
-
- is related to
-
JENKINS-24357 Jenkins 1.535+ versions do not work on Solaris 10
-
- Open
-
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
src/java/winstone/HostConfiguration.java
http://jenkins-ci.org/commit/winstone/ec38d13bcacb4007a797771188360d8a33c9c9fc
Log:
[FIXED JENKINS-22442]
Jetty doesn't let us control where the files are to be exploded, so do
the extraction by ourselves.