Hi anteid - are you able to confirm what the "file structure" image is supposed to be showing (i.e. the contents of the ZIP file or the build directory on the Jenkins server as the files showing as 404 in the browser console view don't appear in the "file structure" image. Also sharing your config would be useful for replication purposes. Thanks

Hi Richard Bywater - That structure is from downloaded ZIP.

I added here zip file "Jenkins issue.zip" so you can see configuration, console output, and report.

thx,

A.

Thanks - just taking a look at the attached console log it appears that the HTML directory in the config was set to "D:\jenkins_prod\workspace\test_9111\Schedules\test95_2_vise_usera\test95_2_vise_usera.stats.html" which looks more like a filename than a directory where the files are getting put. Is that just a case of the wrong config being attached to the issue? (Don't know much about RPT but by the looks of the console logs probably should be set to "D:\jenkins_prod\workspace\test_9111\Schedules\test95_2_vise_usera\"  and perhaps Index Page set to "test95_2_vise_usera.stats.html"?

"D:\jenkins_prod\workspace\test_9111\Schedules\test95_2_vise_usera\test95_2_vise_usera.stats.html" is valid folder. In it are all files (see .zip).

Hi anteid - sorry for the delay but I think I have found the issue is not with the HTML Publisher plugin but with the Javascript that is included with the RPT output.

Basically it looks like when the page loads, it looks to see if the page is being served up using the file:// type protocol (which it would be when looking at locally from the zip) or if "force offline" is enabled (I have no idea how that gets set as it seems to the a RPT Javascript thing). If one of these conditions is true, it goes into some kind of offline mode and works with no issues.

If those conditions aren't met however, it attempts to fetch stuff from "/analytics" and when that fails it appears to stop processing and just give you a blank screen. Obviously it will never be able to get the "/analytics" endpoint on Jenkins.

Only thing I can think of is to find out, if you don't know already, how to force the offline mode to be set and then it will work perfectly. (I tested by taking the ZIP file contents and publishing that to HTML Publisher, and then manually debugging the Javascript and forcing offline and it showed with no issues within Jenkins).

Going to close this issue for now but please feel free to comment if new information comes to hand.

Thank you, r2b2_nz . 

I don't know how to force the offline mode, if you can please write here how you set up that forcing offline mode.

br, and again thank you  for your help,

A:

Update to this thread and r2b2_nz . 

IBM has provided solution patch: TP_57096_HotFix_1.0.0

Thank you, and best regards,

Ante.