[JIRA] (JENKINS-57385) Found "HTTP ERROR 404" in html publish report after running my newman scripts

malay.p@ezdi.us (JIRA)

unread,

May 9, 2019, 6:54:03 AM5/9/19

to jenkinsc...@googlegroups.com

Malay Parikh created an issue

Jenkins /

JENKINS-57385

Found "HTTP ERROR 404" in html publish report after running my newman scripts

Issue Type:	Bug
Assignee:	Richard Bywater
Attachments:	2019-05-09_161318.png, 2019-05-09_161443.png, 2019-05-09_161645.png
Components:	htmlpublisher-plugin
Created:	2019-05-09 10:53
Environment:	Jenkins ver. 2.164.2 htmlpublisher 1.18
Labels:	jenkins plugin windows
Priority:	Major
Reporter:	Malay Parikh

I had run my postman's scripts via newman in Jenkins.

Build was success but still I am not able to get HTML report and found below error :

HTTP ERROR 404

Problem accessing /job/Jenkins_Newman_Tests/HTML_20Report/index.html. Reason:

Not Found

Powered by Jetty:// 9.4.z-SNAPSHOT

Here, I am attaching some screenshot and configuration for more details.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

richard@bywater.nz (JIRA)

unread,

Jul 4, 2019, 5:01:02 AM7/4/19

to jenkinsc...@googlegroups.com

Richard Bywater commented on

JENKINS-57385

Re: Found "HTTP ERROR 404" in html publish report after running my newman scripts

Are you able to confirm there is an index.html in the APIs\newman directory?

Add Comment

richard@bywater.nz (JIRA)

unread,

Sep 13, 2019, 2:37:02 AM9/13/19

to jenkinsc...@googlegroups.com

Richard Bywater commented on

JENKINS-57385

Re: Found "HTTP ERROR 404" in html publish report after running my newman scripts

Just following up with my request for info - if none is provided unfortunately there isn't enough to go on and so I'll need to close the issue. Thanks

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

richard@bywater.nz (JIRA)

unread,

Oct 20, 2019, 4:05:03 AM10/20/19

to jenkinsc...@googlegroups.com

Richard Bywater closed an issue as Incomplete

Hi - as I don't currently have enough information to proceed with looking at this bug, I'm going to close it off for now. If you are able to provide further info then please re-open and provide the requested info.

Thanks