[JIRA] [junit-plugin] (JENKINS-22747) Add Job Configuration Option to NOT fail JUnit Report publish when no xml report files

adjohnson916@gmail.com (JIRA)

unread,

Jul 20, 2015, 11:19:03 AM7/20/15

to jenkinsc...@googlegroups.com

Anders Johnson commented on

JENKINS-22747

Re: Add Job Configuration Option to NOT fail JUnit Report publish when no xml report files

+1

I'd like to be able to configure this plugin so that it won't mark as failed or unstable when no report files are found.

Here's failure output for that scenario in Jenkins ver. 1.607:

 
                                                    Recording test results
ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception
hudson.AbortException: No test report files were found. Configuration error?
	at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:116)
	at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:93)
	at hudson.FilePath.act(FilePath.java:989)
	at hudson.FilePath.act(FilePath.java:967)
	at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:90)
	at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:120)
	at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:137)
	at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670)
	at hudson.model.Run.execute(Run.java:1766)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:374)
 
                                                

Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

cvenegas@esri.com (JIRA)

unread,

Jul 23, 2015, 4:30:10 PM7/23/15

to jenkinsc...@googlegroups.com

Christian Venegas commented on

JENKINS-22747

Re: Add Job Configuration Option to NOT fail JUnit Report publish when no xml report files

+1 here as well. We create jUnit files that fail to be parsed by xUnit. jUnit doesn't have any issues parsing them but if we don't create test files, we get build failures instead of just setting it to unstable or letting it pass.

Add Comment

landolt@royalsys.com (JIRA)

unread,

Oct 15, 2015, 10:09:07 AM10/15/15

to jenkinsc...@googlegroups.com

Paul Landolt reopened an issue

Reopened as this issue has not been resolved.

During the "Publish JUnit test result report" Post-build step, the JUnit XML files are collected and processed. If there are no files to collect (e.g., no unit tests written) then the step fails with the message:

ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception
hudson.AbortException: No test report files were found. Configuration error?

While there may be code in place to not fail skipped test, there is no handling of the situation where there are intentionally no JUnit tests.

I manage 300 jobs from templates. It would be onerous to go into jobs and add / remove reporting manually based on the existence or absence of unit test reports.

Compare this to the "Publish Cobertura Coverage Report" post-build step, which has the option to ignore "Fail builds if no reports"

Jenkins /

JENKINS-22747

Add Job Configuration Option to NOT fail JUnit Report publish when no xml report files

Change By:	Paul Landolt
Resolution:	Fixed
Status:	Resolved Reopened

Add Comment

landolt@royalsys.com (JIRA)

unread,

Oct 19, 2015, 8:12:02 AM10/19/15

to jenkinsc...@googlegroups.com

Paul Landolt assigned an issue to Paul Landolt

I'll take this one. I've worked up a solution. I'll create a branch, get the code in, and make it available for peer review.

My current solution does not have any unit tests, I would really like some input to this as I'm not clear on how to test a plugin without it being installed and on an active Jenkins instance.

Jenkins /

JENKINS-22747

Add Job Configuration Option to NOT fail JUnit Report publish when no xml report files

Change By:	Paul Landolt
Assignee:	Paul Landolt

Add Comment

landolt@royalsys.com (JIRA)

unread,

Oct 19, 2015, 8:14:01 AM10/19/15

to jenkinsc...@googlegroups.com

Paul Landolt commented on

JENKINS-22747

Re: Add Job Configuration Option to NOT fail JUnit Report publish when no xml report files

If I'm going to create a branch, should I name the branch "JENKINS-22747", or is there a protocol for such a thing from an unvetted participant?

Add Comment

o.v.nenashev@gmail.com (JIRA)

unread,

Oct 19, 2015, 4:12:01 PM10/19/15

to jenkinsc...@googlegroups.com

Oleg Nenashev commented on

JENKINS-22747

Re: Add Job Configuration Option to NOT fail JUnit Report publish when no xml report files

Hi Paul,

If you crate a branch in your own fork, feel free to set up any name. The only recommendation is to reference the issue in the pull request title and commits.

Add Comment

landolt@royalsys.com (JIRA)

unread,

Oct 19, 2015, 4:20:02 PM10/19/15

to jenkinsc...@googlegroups.com

Paul Landolt commented on

JENKINS-22747

Re: Add Job Configuration Option to NOT fail JUnit Report publish when no xml report files

Will do. I'm just finishing some live testing with the work I've done. I should be able to check in (or push request, or whatever it's called in GIT) the changes within the next 24 hours so that it can be reviewed.

And it does require at least 2 unit tests, so if you see the best way to test them during review, please let me know; I'd like get the chance to learn more regarding testing this particular plugin.