Our CodeCoverage reports on Jenkins are no longer viewable - when you click the link in the menu we now see a blank screen with no tabs and no content, just the "Back to build" and "zip" links. Clicking the "zip" link allows the report to be downloaded, and it can be opened locally. Opening the Chrome dev tools, there is an error "Uncaught TypeError: Cannot read property 'setAttribute' of null"
Hi Henry Wilson - are you able to share a screenshot or similar of the HTML Publishing configuration too for reference? Also did this work on a previous version of the plugin and it has stopped working with the release of 1.19?
Thomas Gimpel if you could please share your config for the HTML publisher and some background info that would be great as perhaps there's a particular use-case that was missed in the change.
Georgi Georgiev is there an easy way to roll back to the previous version? Annoyingly the Jenkins UI only ever presents the latest version to install...
Henry Wilson if you go to Manage Jenkins / Manage Plugins and go to the Installed plugins tab, there hopefully is a Downgrade button there to take you back to 1.18.
I've tried to reproduce locally but unfortunately as of yet haven't been able to. I'll keep on trying but in the meantime if you are having the issue are you able to produce a directory listing of your the directory in the workspace represented by reportDir (and subdirectories if applicable) just so I can get a feeling for what is present to see if there's anything different to what I'm testing.
Also if anyone can share the portion of the log that relates to HTML publisher that would be great (The section should start along the lines of "[htmlpublisher] Archiving at...")
[2019-09-25T04:05:46.934Z] [htmlpublisher] Archiving HTML reports...
[2019-09-25T04:05:46.935Z] [htmlpublisher] Archiving at BUILD level /jenkins/workspace/Project_Project_feature_develop5.0/testresults/smoketest to /var/lib/jenkins/jobs/Project/jobs/Project/branches/feature-develop5-0.8a6oo2/builds/881/htmlreports/Smoke_20test_20result
Thanks that reconciles my theory. Taking another look at the code it will only work currently if the job is run on the same machine as the Jenkins master. As its going to take a little while to solve that, I'm reverting the change and will be pushing out 1.20 soon which will revert the functionality back to the way 1.18 is working.
[htmlpublisher] Archiving at BUILD level /opt/jenkins/workspace/Mask/Mask1/Mask2@3/791/Mask3/Mask4/test-output to /opt/jenkins/jobs/Mask/jobs/Mask1/jobs/Mask2/builds/791/htmlreports/MyReport
Please note that for the log, I have replaced real directories names with tokens("Mask", "Mask1"...), but values are still 1:1 matching in the source and target dir paths(example "Mask1" value in source dir is the same as "Mask1" value in target)
Log: {code:java} [htmlpublisher] Archiving at BUILD level /opt/jenkins/workspace/Mask/Mask1/Mask2@3/791/Mask3/Mask4/test-output to /opt/jenkins/jobs/Mask/jobs/Mask1/jobs/Mask2/builds/791/htmlreports/MyReport {code}
Please note that for the log, I have replaced real directories names with tokens("Mask", "Mask1"...), but values are still 1:1 matching in the source and target dir paths(example "Mask1" value in source dir is the same as "Mask1" value in target)