|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I suggest most people to first take a look in the TEMP folder on the jenkins server machine.
Are you cleaning your TEMP directory? Do you have any scripts running that periodically cleans the TEMP directory? Or does an admin sometimes clean the directory or run tools like CCleaner (on Windows), etc... ?
This applies esp. to people running jenkins on Windows using the (embedded) Jetty. I guess people running jenkins in tomcat etc. don't have the issue?
When running the Windows service, jetty extracts the war into (example) : TEMP\jetty-0.0.0.0-8080-jenkins.war--any-\webapp
It serves those files (images, .css, etc...) while running.
If you cleanup your TEMP - or at least some files from jetty's temp directory - while jenkins is still running, you'll get 404 errors, because jetty can't find the requested files anymore.