-
Bug
-
Resolution: Fixed
-
Critical
-
None
It was working earlier, and on upgrade on ubuntu packages (apt-get upgrade), jenkins have got upgraded to 1.629 and I find all my jobs which were publishing html file, the html viewer is broken and even the shown zip link doesn't work (refer screenshot)
+ even the saved HTML in build artifact doesn't open with proper html, css. it opens vim like ugly style.
Very Strange thing to note:
even the confix.xml used to say <version>1.629</version> before upgrade and saya the same now as well but yes I can find the difference in Jenkins UI to say that its upgraded (its tabbed UI like jenkins 2 though I get notification to upgrade it to jenkins 2)
Is upgrading to 2 is only solution or will it make worse?
- duplicates
-
-
- Closed
-
- is blocked by
-
JENKINS-65344 HTML Publisher Report CSS not loading for https/secure Jenkins URL
-
- Resolved
-
[JENKINS-38663] HTML viewer is broken in version:1.629
thanks a lot Mcrooney for pointing into right direction. finally after trials and checking errors in devtools figure the working policy for me. noting its here so as to be useful for others facing the same issue
System.setProperty("hudson.model.DirectoryBrowserSupport.CSP","'unsafe-inline';'allow-scripts' ;")
pooja shah
added a comment - - edited thanks a lot Mcrooney for pointing into right direction. finally after trials and checking errors in devtools figure the working policy for me. noting its here so as to be useful for others facing the same issue
System.setProperty("hudson.model.DirectoryBrowserSupport.CSP","'unsafe-inline';'allow-scripts' ;") however Mcrooney: i'm curious to figure how to even resolve these warnings, though till now i dnt see any side effects and even this discussion confirms it http://stackoverflow.com/questions/12291258/unrecognized-content-security-policy-directive
I tried as Mike's ideas but results the same, if i use default-src etc, it doesn't work
pooja shah
added a comment - - edited however Mcrooney: i'm curious to figure how to even resolve these warnings, though till now i dnt see any side effects and even this discussion confirms it http://stackoverflow.com/questions/12291258/unrecognized-content-security-policy-directive
I tried as Mike's ideas but results the same, if i use default-src etc, it doesn't work
mcrooney
added a comment - Duplicate of https://issues.jenkins-ci.org/browse/JENKINS-38663, see for it for resolution 
mcrooney
added a comment - Duplicate of https://issues.jenkins-ci.org/browse/JENKINS-38663 , see for it for resolution 
Please see https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy and particularly the section on HTML Publisher.