search

jenkinsci / code-coverage-api-plugin

Deprecated Jenkins Code Coverage Plugin
https://plugins.jenkins.io/code-coverage-api/
MIT License
111 stars 77 forks source link

Add support for empty results #723

Closed enys closed 8 months ago

enys commented 1 year ago

The coverage step should add support for empty results:

  1. when there are no input files found
  2. when there is no coverage information in an existing file

It makes sense to re-use the existing property failOnError for both cases, see https://www.jenkins.io/doc/pipeline/steps/code-coverage-api/#recordcoverage-record-code-coverage-results.

In both cases a new UI needs to be designed that takes care of such an edge case.

Note that the second requirement needs to be implemented in the https://github.com/jenkinsci/coverage-model library.

uhafner commented 1 year ago

Can you please clarify your requirement? Which one are you interested in:

xpicio commented 1 year ago

@uhafner i suppose should be useful both requirements 🙂

uhafner commented 1 year ago

I updated the documentation. PRs are always welcome 🙏