-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Blocker
-
Component/s: clover-plugin
-
None
-
Environment:Clover plugin version: 4.7.1
Jenkins version: 2.176.1
I tried to implement Clover plugin code coverage.
My requirement was to mark the build as unstable whenever a threshold is not crossed.
Â
Out of the 3 Jenkins jobs it is implemented in, only one's build is marked unstable.
The others are marked successful, despite all 3 having the same threshold values.
Â
I have checked that the coverage report is published in all the three projects.
Â
Under what conditions does a clover plugin not a mark a build "Unstable", even if the actual coverage is less than the threshold?
Â
Please let me know if any more information is required.