Ullrich Hafner
Ullrich Hafner
No, there are no snapshots available right now. You need to wait for the beta version. You can watch PR #512 to see when it is merged.
> The plugin page (https://plugins.jenkins.io/code-coverage-api/) still has the entry but these endpoints are not available anymore.. Yes, the documentation needs to be updated as well. Feel free to submit a...
The new step `recordCoverage` is now in [beta testing](https://github.com/jenkinsci/code-coverage-api-plugin/releases/tag/v4.0.0), can you please check if this release helps to solve this issue? Please note that the syntax of the step is...
This is not possible since I am using features of Jenkins 2.385.
The new step `recordCoverage` is now in [beta testing](https://github.com/jenkinsci/code-coverage-api-plugin/releases/tag/v4.0.0), can you please check if this release helps to solve this issue? Please note that the syntax of the step is...
Yes, I can do that. Are you using the plugin on your own or why are you interested in this issue? The implementation should be quite similar to https://github.com/jenkinsci/warnings-ng-plugin/blob/master/plugin/src/main/java/io/jenkins/plugins/analysis/core/model/ReportScanningTool.java#L154. The...
@YashSalve695 Sorry, seems that I already fixed that in #512.
Yes, when the #512 is released then a lot of small things should be required. But until then it does not make sense to help...
> Has there been any progress on this? I am still facing issues with the default setup, thus I patch the offending sections through Tampermonkey (lines of interest from a...
Yes, that is the idea at some point. I did not find a way yet to handle the line annotations (coverage) in prism. Interested in trying to add support for...