>From looking at the source, it appears Jenkins doesn't actually set
maven.test.failure.ignore. It modifies the testFailureIgnore property of
the surefire plugin. Curiosity satisfied. I'll just specify
maven.test.failure.ignore=true in my project build configuration.
On Wednesday, May 8, 2013 4
I'm using the ${maven.test.failure.ignore} property in my pom.xml and my
test runner returns 0 even with failed tests if I explicitly set the value
with the '-Dmaven.test.failure.ignore=true' switch. But when I run the
build in Jenkins without any explicit command line switches, it's not set
to
If you're using the Maven project type, it publishes the test results
automatically, so there's nothing else to configure. If you're using a
freestyle project, all you need to do is check the appropriate publish test
report post-build action, and it will automatically downgrade a successful
bui
Aha. Thank you, Dean. That's a good first step. I can add some Maven
configuration and change my test runner to return zero as needed. And then
to indicate to Jenkins that I want to downgrade the build from successful
to unstable? I'll look into outputting test results in a format consumable
by
Hi Rob,
Usually, build steps that return with a non-zero exit code is what marks
a build as failed. Test reporters, like the built in Junit reporter, can
downgrade a build from successful to unstable if it discovers failed tests
in the test results. It sounds like the maven-nar-plugin might be
I'm attempting to use Jenkins for CI of a C++ project which is built using
the maven-nar-plugin. I'd like to know how I could better integrate the
nar-plugin with Jenkins so that failed tests do not cause a broken build,
but instead cause an unstable build, as with JUnit tests for Java. The nar
