commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brent Worden <>
Subject Re: [All] Jenkins nonsense (?)
Date Thu, 17 Aug 2017 13:56:51 GMT
The last success in the build log indicates the last execution of Maven was
successful and not that the entire Jenkins build was successful.

Sprinkled throughout the build log are messages of the form 'Skipping
reporter since build result is FAILURE.'  The first such message appeared
shortly after the first occurrence of:
[CHECKSTYLE] Successfully parsed file
of module Apache Commons RNG with 0 unique warnings and 0 duplicates.
at sun.reflect.GeneratedMethodAccessor15682.invoke(Unknown Source)
[PMD] Skipping reporter since build result is FAILURE

So, the build if failing trying to either generate the checkstyle report or
generate the PMD report.  I say this because it is not clear from the
exception what Maven stage is actually running at the moment of failure.
Adding --debug to the Maven command might provide better insight into the
actual cause.


On Thu, Aug 17, 2017 at 7:38 AM, Gilles <>

> Hello.
> Does someone know why Jenkins reports a build as "Failed" while
> the last line of the console output is:
> ---CUT---
> Finished: SUCCESS
> ---CUT---
> See e.g.
> RNG__Java8/50/console
> Note that for the same code Jenkins reports success in another job:
> Rng/138/console
> The only (intended) difference is "Java 8" vs "Java 6".
> Regards,
> Gilles
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message