-
New Feature
-
Resolution: Fixed
-
Major
-
None
It would be very useful to add support for ratcheting. This would involve making the build job fail or become unstable if the code coverage for a build drops below the code coverage of the previous build. The plugin could keep track of the highest code coverage metrics values from previous builds, and check against this. If the current results are lower, the build fails. If not, the latest values are stored as the new reference values.
This is very useful for legacy projects, where you want to adopt a Continuous Improvement strategy rather than just imposing a minimum required level of test coverage.
Thoughts?
- is related to
-
JENKINS-22018 Support for ratcheting of minimum thresholds in Jacoco coverage
-
- Open
-
-
JENKINS-11025 Allow the build to fail on low coverage
-
- Resolved
-
I'd also like to have support for failing the build when the coverage gets worse than it was.
I've been looking at different options like:
It'd be super-nice if the Cobertura plugin supported "ratcheting" limits like this but I'd be happy if it were obvious how to source the thresholds from anywhere other than a fixed value in the Web interface.
(FWIW, I don't think this is a duplicate of
JENKINS-11025– that only covers static thresholds, this ticket covers dynamic thresholds)