Re-executing the JUnitParser is going to be very expensive for builds with a large number of unit tests. When I've considered this sort of thing in the past, I was pretty certain that it would require 'help' from the project itself, so that the parser can be made aware of newly-available test results. Otherwise, you're basically polling, which we all know is evil :-)
----- Original Message ----- From: [email protected] To: [email protected] At: Aug 8 2013 11:57:57 I've not used the plugin, since it does require some extra setup on the project side, such as extra jar, and tests setup with a specific runner, or something like that. You might want to contact the plugin maintainer for more help or information. -- Larry On Thu, Aug 8, 2013 at 9:41 AM, ogondza <[email protected]> wrote: Thanks, never heard about the plugin before. This seems to require assistance from the project being built, right? I simply rerun JUnitParser to collect report files regardless where did they come from. Perhaps I'm wrong. I do not have enough time try it out. -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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.
