-Original Message-
From: Matt Walsh
Sent: Friday, April 27, 2012 9:26 AM
To: users@maven.apache.org
Subject: RE: Maven failed with error while reading test results
Doesn't look like maven failed. Your tests failed, which caused your
build to fail, then Jenkins failed looking
Doesn't look like maven failed. Your tests failed, which caused your
build to fail, then Jenkins failed looking for results.
Maybe you've configured your Jenkins build to do it's post processing
even on failure?
Matt
-Original Message-
From: Alexis Morelle
Please refer to
D:\Jenkins-slave\workspace\jobname\modulename\target\surefire-reports
for the individual test results.
Does the log literally say jobname and modulename? If so, this
suggests an error in how Jenkins is calling your Maven build (to me at
least).
[JENKINS] Archiving
The thing is that if I add -fn for example (never fail), the build ends
successfully.
Anyway I just saw something even more strange with the following log.
It says: [INFO] Error for project: CMS - XML Engine Implementation
(during install)
But then: [INFO] Internal error in the plugin manager
Lol don't consider that, that was a lame attempt to obfuscate few
internal details as asked by my company...
See my next answer for more details with normal logs, sorry about that.
Alexis.
Le 27/04/2012 17:37, Wayne Fay a écrit :
Please refer to
-
From: Alexis Morelle [mailto:alexis.more...@alcatel-lucent.com]
Sent: Friday, April 27, 2012 9:42 AM
To: Maven Users List
Subject: Re: Maven failed with error while reading test results
The thing is that if I add -fn for example (never fail), the build ends
successfully.
Anyway I just saw
, April 27, 2012 9:42 AM
To: Maven Users List
Subject: Re: Maven failed with error while reading test results
The thing is that if I add -fn for example (never fail), the build ends
successfully.
Anyway I just saw something even more strange with the following log.
It says: [INFO] Error for project
