6

I run Jenkins for my continuous integration and I have the following problem. After a couple of days Jenkins is running totally fine, the URL for static files stop being served and the CSS, JavaScript and global look of Jenkins looks broken when it actually runs the jobs as expected.

Any idea why?

Example of an URL:

http://myserver:8181/static/70f4ebef/css/style.css

Response:

HTTP ERROR 404

Problem accessing /static/70f4ebef/css/style.css. Reason:

    Not Found
Powered by Jetty://

Calling http://myserver:8181/safeRestart fixes the problem so I'm wondering if it's a Jenkins issue or a Jetty/Jenkins cache conflict.

I run Jenkins 1.537.

Mick F
  • 7,312
  • 6
  • 51
  • 98

1 Answers1

4

It's happening because the static resources are unpacked in your /tmp directory and something else is cleaning up files older than x number of days old in there.

Refer to Jenkins issue 17526 for more info.

Chris Heller
  • 66
  • 1
  • Seems very relevant. I've given another tmp dir location to the JVM I'm using (cf. http://stackoverflow.com/questions/1924136/environment-variable-to-control-java-io-tmpdir). Will let you know how it goes in a couple of days ;) – Mick F Dec 12 '13 at 14:17