-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins ver. 1.643,
HTML Publisher plugin 1.10
I publish several HTML reports after a build and after sorting out the Content Security Policy updates, one error remains.
Checksum mismatch
The checksum of the current wrapper file (5ea0d2ed1f4d0710e3ceaa8d2c3d9b35a3a13475) does not match the recorded checksum (6db1021567d9b39bdcd2b32a86e1dad589f620dd). This indicates a possible security issue, therefore Jenkins will not serve this file. You can access the archived HTML files here.
I don't know what this means or how to address it and I can't find any information in the HTML publisher plugin docs. Each report is configured like this one:
The problem only occurs when I click on the project-level report link, for example:
https://example.com/job/ExampleProject/Tests/
If I click the build-specific report, it displays fine, for example:
https://example.com/job/ExampleProject/101/Tests/
The same problem goes unanswered on Stack Overflow: http://stackoverflow.com/questions/34419223/jenkins-html-publisher-plugin-checksum-mismatch
- links to
[JENKINS-32281] HTML report shows "Checksum mismatch"
jonw (and everyone else watching): Proposed fix at https://github.com/jenkinsci/htmlpublisher-plugin/pull/23
Please take a look, maybe give the PR build https://jenkins.ci.cloudbees.com/job/plugins/job/htmlpublisher-plugin/61/ a try?
Thanks for the quick fix. I only tested it superficially, but it looks good.
Joachim Nilsson
added a comment - I also tested it briefly, looks OK for me as well. > Note: I cannot reproduce the error if I only create 2 reports, I also must mark the publishing option: 'Keep past HTML reports'
This was my experience as well but I was unsure about it and not sure if it was relevant.
Yep, it's important, otherwise a different branch in the code is taken. So you need a) multiple reports per build, b) archiving reports of past builds, c) access reports through project-level links. Therefore the instructions how to reproduce the issue were essential.
(This is really a bit of a hack because if you archive reports for past build, it switches to a different mode in which reports are attached to builds rather than to the project, and the project-level links essentially forward to the build-level archive… and that's where I messed up the checksum change for 1.10 – but it's only apparent when you archive multiple different reports.)
Code changed in jenkins
User: Daniel Beck
Path:
src/main/java/htmlpublisher/HtmlPublisherTarget.java
http://jenkins-ci.org/commit/htmlpublisher-plugin/014ee3838bc5a617e2cf6474423099c34e947abe
Log:
[FIX JENKINS-32281] Consider multiple reports per build
Code changed in jenkins
User: Mike Rooney
Path:
src/main/java/htmlpublisher/HtmlPublisherTarget.java
http://jenkins-ci.org/commit/htmlpublisher-plugin/9dd6fe1ea02d48ea411125b54369752f5be4f494
Log:
Merge pull request #23 from daniel-beck/JENKINS-32281
[FIX JENKINS-32281] Consider multiple reports per build
Compare: https://github.com/jenkinsci/htmlpublisher-plugin/compare/4a8d86addf84...9dd6fe1ea02d
mcrooney
added a comment - Released as HTML Publisher 1.11, let us know how it works for you I converted all of my custom reports to plugin-based-reports! If no one else can repro the fix, I'll try to spin up one of my older configurations.
Same issue
RHEL 6.5
Jenkins 1.645
HTML Publisher plugin 1.10
Output from script console: UTF-8
Great finding Jon! Yes that is applicable for us as well, we have several reports per job.
Note: I cannot reproduce the error if I only create 2 reports, I also must mark the publishing option: 'Keep past HTML reports'