Ullrich Hafner
Ullrich Hafner
The old step is too tightly coupled with the old model and cannot be refactored so that old pipelines will remain compatible.
The previous coverage model supports a [remote API](https://www.jenkins.io/doc/book/using/remote-access-api/) to obtain the coverage results. This needs to be added for the new model as well. Old implementation: https://github.com/jenkinsci/code-coverage-api-plugin/blob/master/plugin/src/main/java/io/jenkins/plugins/coverage/targets/RestResultWrapper.java New implementation should...
Currently, all colors are hard-coded. It would be helpful, if those could be changed by the user. The following Colors that should be configurable: - trend chart line and branch...
The tree map click event currently zooms into the tree chart. It would make more sense if the corresponding file details view will be opened.
UI improvement for #203 Currently the trend shows line and branch coverage. It should be configurable, which of the coverage metrics should be shown. Current configuration dialog: 
If there is more than one report then the build summary shows details for all coverage node levels. It might make sense to restrict these to line and branch as...
See #342. The first two commits have been moved to a separate branch so that GitHub UI will not freeze during reviews anymore.
Otherwise maven build will break: ``` [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 2.920 s [INFO] Finished at: 2022-09-11T15:49:37+02:00 [INFO] ------------------------------------------------------------------------ [WARNING] The requested profile "no-ui-tests-on-mac" could...