Since version 1.2, any test case failure by default triggers maven build
failure. This is not expected in all the cases. For example, if a Jenkins build
is unstable (which means build successful but test cases failure, Jenkins will
display the failed test cases on the job front page. If the build is failure,
it will not display the failed test cases on the job front page.
So I add a new parameter "failBuildOnTestFailure" in the configuration to
enable this maven build failure trigger. Default value is true which means the
current behavior will not change. Any test case failure continue triggers maven
build failure. But you can set it as false to turn off the trigger.
Here I attach the diff.
Original issue reported on code.google.com by
henryzho...@gmail.comon 9 May 2013 at 6:46Attachments: