Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
The current implementation of Hudson's Maven support needlessly requires the use of maven-surefire-plugin for executing tests. If an alternative test runner plugin is used, Hudson's maven-plugin will not recognize test results, meaning that UNSTABLE builds are wrongly considered to be FAILED builds, and also that build status does not include test result reports.
This behavior is due to the fact that the SurefireArchiver class includes conditional logic that insists that the test runner plugin is Surefire. If this conditional check is removed, then test results are correctly found and interpreted, and unstable builds are no longer considered failed builds.
I've attached a simple patch that demonstrates this. Even though the contents of the patch may not be the correct fix, it at least illustrates the nature of the problem.
Attachments
Issue Links
- is blocking
-
JENKINS-16121 maven-soapui-plugin configurable outputFolder
-
- Resolved
-
- is duplicated by
-
JENKINS-13188 Recognize test results from com.github.searls:jasmine-maven-plugin
-
- Resolved
-
- is related to
-
JENKINS-16776 surefire-reports not detected for android-maven-plugin
-
- Resolved
-
Integrated in
jenkins_main_trunk #2201
Changelog and cleanup for
JENKINS-8334(Revision 6b1cc47024172238a65d45f28db84f13495d8780)Result = SUCCESS
Christoph Kutzinski : 6b1cc47024172238a65d45f28db84f13495d8780
Files :