Have you tried passing -fn (fail never) option when you invoke a build?
mvn test site -fn
That should continue the build inspite of any failures.
HTH,
Rahul
pjungwir wrote:
Suppose you say this:
mvn test && mvn site
That gives you a failure but not a site. And if you say this:
mvn test; mvn site
you get a site but not a failure.
So what if you wrote a quick plugin that checks for errors in the surefire
reports? Then you could say:
mvn test; mvn site; mvn my-group:check-for-failures
Paul
jp4 wrote:
I am interested in what you did. We use CC as well. Any info you can
provide would be greatly appreciated. This is very important as we have a
huge codebase and would like to identify all errors every night (NOT JUST
THE FIRST ONE!)
Thanks,
jp4
Jon SlinnHawkins wrote:
TestFailureIgnore will then result in a build success. When infact the
tests failed, so the build needs to be failed.
I had exeactly the same issue.
We are using CruiseControl for our Continuous Integration system.
Unfortunately I had to modify the CC code. It was only a minor change
but
it has enable us to
execute maven 3 times as part of the same build, if any of the 3 runs
fail
the build will continue until all 3 are finshed and THEN report a build
failure.
FYI -
1 - Checkout source and cleanup folders
2 - Maven deploy (inculding unit and functional testing)
3 - Build the site.
If you are using CC i will try and find the peice of code i changed. It
was
a very simple change.
Cheers
Jon
"Alexandre Russel" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
