When coverage goes down threshold is updated and the build is not marked as unstable

Using the snippet generator I’ve added the following step to my Jenkinsfile:

cobertura coberturaReportFile: 'coverage.xml', conditionalCoverageTargets: '80, 0, 0', failUnhealthy: true, failUnstable: true, lineCoverageTargets: '80, 0, 0', maxNumberOfBuilds: 0, methodCoverageTargets: '80, 0, 0', onlyStable: false, sourceEncoding: 'ASCII', zoomCoverageChart: false

This should set the initial threshold to 80% for lines, methods and conditionals and auto-update the minimum when the build is successful (as autoUpdateHealth and autoUpdateStability are true by default). But when coverage goes down the threshold is updated and the build is not marked as unstable:

The pipeline steps reports the update of the thresholds:

    Methods's new health minimum is: 78.84
    Lines's new health minimum is: 82.19
    Conditionals's new health minimum is: 72.23
    Methods's new stability minimum is: 78.84
    Lines's new stability minimum is: 82.19
    Conditionals's new stability minimum is: 72.23

In other non-pipeline jobs using the cobertura-plugin, when the coverage is bellow the minimum the coverage does not get updated and the build is marked as unstable.

Environment

• Jenkins v.2.73.3
• Cobertura plugin v1.12
• Pipeline plugin v2.5
• Pipeline: API plugin v2.23.1

[sackdan]

Any news on this front?

[cizezsy]

@lexotero I think the third value in the methodCoverageTargets option is used for stable threshold, so it won’t mark build as unstable as you config it to zero.