On Monday, 17 July 2017 21:42:50 UTC-4, Evgeny Mandrikov wrote: > Hi, > > > > Jenkins JaCoCo Plugin is not developed by JaCoCo team and unfortunately > developers of Jenkins plugin do not read this mailing list , but have a > separate one - > http://groups.google.com/group/jenkins-jacoco-plugin-mailing-list Please > contact them directly. > > > P.S. According to the page > https://wiki.jenkins.io/display/JENKINS/JaCoCo+Plugin support of import of > XML was removed a long time ago (back in 2012). > > On Monday, July 17, 2017 at 4:02:27 PM UTC+2, [email protected] wrote:Hello, > I am fairly new to the Jacoco coverage format, and was looking to integrate > Jacoco coverage results with Jenkins using the Jacoco > plugin(https://wiki.jenkins.io/display/JENKINS/JaCoCo+Plugin). > I wanted to know if there's a way to view code-coverage results from an > existing XML report (well formed and valid according to the DTD in Jacoco > documentation) in Jenkins? > Looking at some blog-posts > (https://dzone.com/articles/jacoco-jenkins-plugin), it seems that such > imports were possible previously, where an XML file was location could be > specified in the "Post-Build Actions" options. This seems to have changed in > the later version, where the user needs to specify location of the .EXEC > files and Sources. > I'm particularly curious about this part, since the Jenkins plugin for the > Cobertura format allows users to import and view results from an XML file. Is > there still a way I can do this using the Jacoco plugin? > > Thank you for any help on this.
Thanks, Evgeny. -- You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/b6b1c12d-4cc5-497e-9658-991c456b4cc2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
