-
Bug
-
Resolution: Not A Defect
-
Critical
-
Jenkins 1.502 / Tomcat 6 / JDK 1.6.0_18 / Debian 6 / x86
Current JaCocO Plugin (using Jenkins 1.502) marks my build as UNSTABLE. But the same build has sufficient minimum coverage. This is totally confusing!
From Log:
[JaCoCo plugin] Thresholds: JacocoHealthReportThresholds [minClass=10, maxClass=100, minMethod=10, maxMethod=70, minLine=10, maxLine=80, minBranch=10, maxBranch=80, minInstruction=10, maxInstruction=80, minComplexity=10, maxComplexity=80]
[JaCoCo plugin] Publishing the results..
[JaCoCo plugin] Loading packages..
[JaCoCo plugin] Done.
Build step 'Publish JaCoCo coverage' changed build result to UNSTABLE
From same build's JaCoCo result:
85% M: 371 C: 2047
68% M: 88 C: 184
69% M: 97 C: 216
85% M: 60 C: 345
84% M: 27 C: 139
Obviously, none of the JaCoCo figures are less under the JaCoCo minimums (10%). So it is a major fault that the plugin marks this build as UNSTABLE.
[JENKINS-16903] JaCoCo Plugin marks build as UNSTABLE, but the coverage was sufficient
If I understand that thread correctly, by intention the former JaCoCo plugin reported UNSTABLE when the coverage was between MIN and MAX? This is strange, because I (and possibly lots of others) would expect a build to be UNSTABLE when below MIN, but to be STABLE (but not perfectly shining) when between MIN and MAX.
So do I understand correctly, that in the next release, the build will be reported as STABLE while coverage is between MIN and MAX, or can you point me to a URL where the exact future policy is described? 
Hi,
This is not a bug, but it will change with the next release.
Check this thread: https://groups.google.com/d/topic/jenkins-jacoco-plugin-mailing-list/pzHm98RJjB8/discussion
Cheers,
Ogi