|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I've just debugged this and it seems like this is a bug in the MavenTestDataPublisher in Jenkins core.
MavenTestDataPublisher is only called for the aggregated MavenModuleSetBuild (and not for the individual MavenBuilds) - which may be okay or not, that's debatable.
However, the bug is that it checks if there is a SurefireReport action attached to the MavenModuleSetBuild, but there is never is one:
MavenModuleSetBuilds only have SurefireAggregatedReports!