[JIRA] [jacoco-plugin] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Akos Kozak edited a comment on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Still not working 100%-ly with plugin version 1.0.16 and Jenkins 1.563. I made a smaller maven project where I got api and be modules. I set: pom.xml check-coverage check BUNDLE *api* LINE COVEREDRATIO 0.25 And the plugin works well. No api is visible in the coverage. But if I do the same on our large project, if from one module Test a call will be done on an api, and therefor in the be classes this will be visible. However I would like to exclude api. Module A A-api: Interface to A service A-be : Service A implementation Module B B-api: Interface to B service B-be: Service B implementation From Service B implementation we call a method over A-api Interface to A service implementation. Therefore, the B-api will be excluded, but the A-api not! This is a bit disturbing, because the A-api should be also excluded. I hope I have right, and it is understandable what I wrote! 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Akos Kozak edited a comment on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Still not working 100%-ly with plugin version 1.0.16 and Jenkins 1.563. I made a smaller maven project where I got api and be modules. I set: pom.xml check-coverage check BUNDLE *api* LINE COVEREDRATIO 0.25 And the plugin works well. No api is wisible in the coverage. But if I do the same on our large project, if from one module Test a call will be done on an api, and therefor in the be classes this will be visible. However I would like to exclude api. Module A A-api: Interface to A service A-be : Service A implementation Module B B-api: Interface to B service B-be: Service B implementation From Service B implementation we call a method over A-api Interface to A service implementation. Therefore, the B-api will be excluded, but the A-api not! This is a bit disturbing, because the A-api should be also excluded. I hope I have right, and it is understandable what I wrote! 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Akos Kozak commented on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Still not working with plugin version 1.0.16 and Jenkins 1.563. Should we update? Or need to be fixed in the plugin! Thank you! 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco] (JENKINS-23588) JaCoCo Plugin creates unreadable coverage report
Akos Kozak commented on JENKINS-23588 JaCoCo Plugin creates unreadable coverage report Also a small hint would be nice there to know what does M and C meaning! 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco] (JENKINS-23857) Coverage Breakdown by Maven Module
Akos Kozak created JENKINS-23857 Coverage Breakdown by Maven Module Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco Created: 17/Jul/14 2:49 PM Description: It would be perfect to see the Coverage per Maven module. We got a bigger project with many-many packages. So, it is not perfect, because we are not able to see which module has bad coverage and which not. Project: Jenkins Priority: Major Reporter: Akos Kozak 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco] (JENKINS-23588) JaCoCo Plugin creates unreadable coverage report
Akos Kozak commented on JENKINS-23588 JaCoCo Plugin creates unreadable coverage report I think the coloured column has somehow a dynamic size. We got the same problem! I just think, maybe to use Emma till this is not fixed, would be maybe a better choice. Please fix this ASAP! Thank you! 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco] (JENKINS-19370) JaCoCo plugin should say on build result page why build failed, if threshold is broken
Akos Kozak commented on JENKINS-19370 JaCoCo plugin should say on build result page why build failed, if threshold is broken I think i case it fails because of the threshold, should the job fail not only the colour/status of the job should be changed. If the coverage drops down, the build should fail, and delvelopers should implement some more Tests, or do something. No email notification will be send if because of coverage the build "fails". 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco] (JENKINS-23823) Trend graph should have percentage value (too)
Akos Kozak created JENKINS-23823 Trend graph should have percentage value (too) Issue Type: Improvement Assignee: Ognjen Bubalo Components: jacoco Created: 16/Jul/14 9:26 AM Description: Trend graph should have percentage value (too) as from the line covered and line missed we could not see, how the percentage changed during the builds. Project: Jenkins Priority: Major Reporter: Akos Kozak 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco] (JENKINS-23822) Wiki page has images in German
Akos Kozak updated JENKINS-23822 Wiki page has images in German Change By: Akos Kozak (16/Jul/14 9:22 AM) Component/s: jacoco Component/s: component 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [component] (JENKINS-23822) Wiki page has images in German
Akos Kozak created JENKINS-23822 Wiki page has images in German Issue Type: Bug Assignee: Praqma Support Components: component Created: 16/Jul/14 9:15 AM Description: On the Page of JaCoCo Wiki (https://wiki.jenkins-ci.org/display/JENKINS/JaCoCo+Plugin) you can find some example images, but in German language. Please change it to English! Thank you! Environment: Wiki Project: Jenkins Priority: Trivial Reporter: Akos Kozak 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.