|
||||||||
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 |
- [JIRA] (JENKINS-15011) Jacoco Plugin 1.0.... ognjen.bub...@gmail.com (JIRA)
- [JIRA] (JENKINS-15011) Jacoco Plugin... drothau...@fcci-group.com (JIRA)
- [JIRA] (JENKINS-15011) Jacoco Plugin... drothau...@fcci-group.com (JIRA)
- [JIRA] (JENKINS-15011) Jacoco Plugin... drothau...@fcci-group.com (JIRA)
- [JIRA] (JENKINS-15011) Jacoco Plugin... be...@dutkowski.net (JIRA)
- [JIRA] (JENKINS-15011) Jacoco Plugin... hmlna...@post.cz (JIRA)
- [JIRA] (JENKINS-15011) Jacoco Plugin... hmlna...@post.cz (JIRA)
- [JIRA] (JENKINS-15011) Jacoco Plugin... hmlna...@post.cz (JIRA)
- [JIRA] (JENKINS-15011) Jacoco Plugin... ognjen.bub...@gmail.com (JIRA)
There is another stack trace displayed when I went to the URL of enlarged JaCoCo coverage graph (i.e. <JOB_URL>/jacoco/graph?width=640&height=480:
Maybe this is due to missing JaCoCo plugin results for previous builds? Those became unreadable after JaCoCo plugin update. If that is the case, I think that there should be a fallback that would return zero coverage for these old builds.