You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would be fine if publishCoverage were only ever called once in a given pipeline, but with the support for calling it multiple times (e.g., using a tag to merge the results), each invocation overwrites any "Code Coverage" check(s) published previously.
The approach used by the JUnit plugin in jenkinsci/junit-plugin#211 would be a good way to solve this by default. Additionally or instead, adding support for the withChecks capability introduced in Checks API 1.2.0 would offer another possible solution.
The text was updated successfully, but these errors were encountered:
Dependencies
Possibly Checks API 1.2.0, depending on the chosen solution.
Feature Request
Currently the Checks name published to GitHub is hard-coded to "Code Coverage":
code-coverage-api-plugin/src/main/java/io/jenkins/plugins/coverage/CoverageChecksPublisher.java
Line 66 in 4399614
This would be fine if
publishCoverage
were only ever called once in a given pipeline, but with the support for calling it multiple times (e.g., using atag
to merge the results), each invocation overwrites any "Code Coverage" check(s) published previously.The approach used by the JUnit plugin in jenkinsci/junit-plugin#211 would be a good way to solve this by default. Additionally or instead, adding support for the
withChecks
capability introduced in Checks API 1.2.0 would offer another possible solution.The text was updated successfully, but these errors were encountered: