-
Bug
-
Resolution: Duplicate
-
Major
-
None
Happens semi-random, but whenever I leave the Jenkins page for an amount of time and then come back and hit refresh, the CSS seems to break (see attached image).
Hitting refresh again does NOT fix it. However, holding shift while refreshing (forced refresh) fixes the issue and the page goes back to looking normal (hitting normal refresh works fine then).
I've tried it in different browsers (and even a co-worker's computer) and it is happening there too.
- duplicates
-
-
- Reopened
-
-
-
- Resolved
-
- is related to
-
-
- Closed
-
[JENKINS-17526] Broken CSS when reloading Jenkins after a time of inactivity
Roberto Andrade
added a comment - This seems to have been resolved on Jenkins 1.555: https://github.com/jenkinsci/jenkins/commit/7c51cec55649b0e46047cb5e3198b66c3bdd94d5
Roberto Andrade
added a comment - This seems to have been resolved on Jenkins 1.555: https://github.com/jenkinsci/jenkins/commit/7c51cec55649b0e46047cb5e3198b66c3bdd94d5 The commit mentioned only fixes Mac OSX, however I have also seen this issue on CentOS 6 (or probably any other Linux or Unix) with tmpwatch installed. I would strongly recommend defaulting to /var/run/jenkins or something similar, across all *nix like OS's. The current workaround is to either edit /etc/default/jenkins to change the tmpdir (similar to the commit), or edit /etc/cron.daily/tmpwatch to exclude it as @akiko_pusu mentioned above. As I don't think the Jenkins package should be futzing with the tmpwatch cron job, it makes the most sense, in my opinion, to default to a different tmpdir location. Note that this would also require the directory to be created with the proper permissions. The /var/run/jenkins directory could be created by the package, but it should be checked and created if necessary during the init script because some OS's (Solaris) tend to mount /var/run on tmpfs.
Tommy McNeely
added a comment - - edited The commit mentioned only fixes Mac OSX, however I have also seen this issue on CentOS 6 (or probably any other Linux or Unix) with tmpwatch installed. I would strongly recommend defaulting to /var/run/jenkins or something similar, across all *nix like OS's. The current workaround is to either edit /etc/default/jenkins to change the tmpdir (similar to the commit), or edit /etc/cron.daily/tmpwatch to exclude it as @akiko_pusu mentioned above. As I don't think the Jenkins package should be futzing with the tmpwatch cron job, it makes the most sense, in my opinion, to default to a different tmpdir location. Note that this would also require the directory to be created with the proper permissions. The /var/run/jenkins directory could be created by the package, but it should be checked and created if necessary during the init script because some OS's (Solaris) tend to mount /var/run on tmpfs. 
Richard Mortimer
added a comment - See JENKINS-22442
It should fix the issue reported here. 
Kevin Wojniak
added a comment - I'm still seeing this issue with 1.556 on OS X 10.9.2. Richard Mortimer
added a comment - The fix for JENKINS-22442 restores the previous behaviour and 1.558 now honours the --webroot commandline argument again.
Richard Mortimer
added a comment - The fix for JENKINS-22442 restores the previous behaviour and 1.558 now honours the --webroot commandline argument again. Fix for JENKINS-22442 in 1.558 and 1.554.1 should resolve this as well. Therefore marking this as duplicate.
Code changed in jenkins
User: Greg Albrecht
Path:
Library/Application Support/Jenkins/jenkins-runner.sh
scripts/postinstall-launchd-jenkins
http://jenkins-ci.org/commit/packaging/c8fb9d70124277b3d64e19a384171fcd396792e3
Log:
JENKINS-17526 Relocating Jetty/Java tmpdir for Mac OS X.
Originally-From: jenkins-ci.org/commit/core/95842fd6b6fe493da6bbb12faa0ec2c5c314f473
Code changed in jenkins
User: Olivier Lamy
Path:
Library/Application Support/Jenkins/jenkins-runner.sh
scripts/postinstall-launchd-jenkins
http://jenkins-ci.org/commit/packaging/c932cd9363357fc83e993b1da2d565ed2893aee1
Log:
Merge pull request #1061 from OnBeep/feature/ampledata-mac_os_x_tmp
JENKINS-17526 Relocating Jetty/Java tmpdir for Mac OS X.
Originally-From: jenkins-ci.org/commit/core/7c51cec55649b0e46047cb5e3198b66c3bdd94d5
Ashish
added a comment - We are facing similar issue with Jenkins. Logged in users are working fine and able to see the UI properly. But unlogged in users are not able to view the UI properly and css/images are messed up for them. The cache containing static content is not available for unlogged in users.
Anyone aware of this issue?
Ashish
added a comment - We are facing similar issue with Jenkins. Logged in users are working fine and able to see the UI properly. But unlogged in users are not able to view the UI properly and css/images are messed up for them. The cache containing static content is not available for unlogged in users.
Anyone aware of this issue? 
I think that this is the same issue as
JENKINS-20682. I added some notes regarding how that might be fixed but don't have the time at the moment to delve into the workings of winstone.jar to make a production ready fix.