-
Bug
-
Resolution: Unresolved
-
Minor
-
Jenkins 2.46.2
Clover plugin 4.7.1
We are using clover plugin to change the build status according to code coverage. Yesterday, Clover plugin stopped modifying the build status. Even though coverage is under user-defined unhealthy limits, build started to have a SUCCESS build result instead of UNSTABLE a few hours ago. The clover.xml report is still there and the HTML report is still published but build status isn't set to UNSTABLE anymore. No update and not change to the Jenkinsfile was done.
Pipeline output displays:
[Pipeline] stepPublishing Clover coverage report... Publishing Clover HTML report... Publishing Clover XML report... Publishing Clover coverage results...
It used to display:
[Pipeline] stepPublishing Clover coverage report... Publishing Clover HTML report... Publishing Clover XML report... Publishing Clover coverage results... Code coverage enforcement failed for the following metrics: Conditionals Setting Build to unstable.
Do you have any debug logs for this?
Do you have the failingTarget set for Clover? I'm asking because the code looks like this:
So as you can see if you have no failingTarget property set in your pipeline config, it will not report any unstable build.