Re: Re: CSS and Images Broken Post LTS 1.480.1 Update?
Hi, I'm glad to be able to eliminate the view as a problem. I originally installed Jenkins as a native package. However, since then I have been upgrading by simply updating the .war file Procedure I used: 1. /etc/init.d/jenkins stop 2. cd /var/lib/jenkins 3. jenkins.war /var/lib/jenkins/jenkins.war.bkp 4. wget http://updates.jenkins-ci.org/download/war/1.480.1/jenkins.war 5. /etc/init.d/jenkins start This is where my system admin abilities are a bit under cooked. Should I be upgrading via a package? On the manage Jenkins page when I click on the update button I download the new .war, which is why I though it was the only thing needed for the update. Please correct me if I'm wrong. Thank you On Tuesday, November 27, 2012 1:11:21 PM UTC-7, vjuranek wrote: > > Hi, > > > It now states "This view has no jobs associated with it." > > I was able to reproduce this by removing read permission for jobs for > anonymous user, so this doesn't seems to be related to the issue. > Unfortunately, I still cannot reproduce the issue itself. Are you running > Jenkins on some servlet container (if yes, which one) or it's installed > from > native package? > > Cheers > Vojta >
Re: Re: CSS and Images Broken Post LTS 1.480.1 Update?
Hi, > It now states "This view has no jobs associated with it." I was able to reproduce this by removing read permission for jobs for anonymous user, so this doesn't seems to be related to the issue. Unfortunately, I still cannot reproduce the issue itself. Are you running Jenkins on some servlet container (if yes, which one) or it's installed from native package? Cheers Vojta
Re: CSS and Images Broken Post LTS 1.480.1 Update?
Thank you for the response. Vojta, I did as you asked and looked if I could load the css via browser by grabbing the link href source from the source code. I was able to pull up the css file for both the style.css and color.css without problem via browser. Here are some more specifics regarding this issue. - Jenkins is running LTS 1.480.1 on CentOS 5 using java 6 - What I've tested - clear cache - Initial load (Not logged in) - Windows -> IE 9 (Broken css and images) - Windows -> FF 18 (Broken css and images) - Windows -> Chrome 64 (Broken css and images) - Apple -> Safari (Broken css and images) - Login - Windows -> IE (Working css and images) - Windows -> FF (Working css and images) - Windows -> Chrome (Broken css and working images) - Apple -> Safari (Working css and images) - Logout - Windows -> IE (Working css and broken images) - Windows -> FF (Working css and broken images) - Windows -> Chrome (Broken css and images) - Apple -> Safari (Broken css and images) On the same thread, but a different note the only other change to our Jenkins installation around the same time I updated to the current Jenkins LTS release was changing the 'All' view. I followed the directions located on the wiki at https://wiki.jenkins-ci.org/display/JENKINS/Editing+or+Replacing+the+All+View. I've noticed that when first loading the homepage the message has changed. Prior to update it said (paraphrasing) "You are not logged in. Login now." It now states "This view has no jobs associated with it." Could this be part of my issue? Is there a way to reset the 'All' view to it's default setting? I'm curious if that is causing some permission issues with the view? I wouldn't mind resting it to default it to try to isolate the issue I'm experiencing. Thank you On Tuesday, November 27, 2012 5:15:06 AM UTC-7, vjuranek wrote: > > Hi, > > > After the update I > > noticed that logged out users have broken CSS. Has anyone else had any > > issues with their CSS after the upgrade? > > no, I didn't spot any such issue. Could you check if you are able to load > the > CSS directly by browser? > E.g. if the link is > href="/static/8990f217/css/style.css"/> > then check if $JENKINS_URL//static/8990f217/css/style.css loads something? > > Btw: which server container do you use? > > Cheers > Vojta >
Re: CSS and Images Broken Post LTS 1.480.1 Update?
Hi, > After the update I > noticed that logged out users have broken CSS. Has anyone else had any > issues with their CSS after the upgrade? no, I didn't spot any such issue. Could you check if you are able to load the CSS directly by browser? E.g. if the link is then check if $JENKINS_URL//static/8990f217/css/style.css loads something? Btw: which server container do you use? Cheers Vojta
