cizezsy on dev
[maven-release-plugin] prepare … (compare)
cizezsy on code-coverage-api-1.0.7
cizezsy on dev
[maven-release-plugin] prepare … (compare)
cizezsy on dev
Fix: thresholds set in global l… Merge pull request #67 from jen… (compare)
cizezsy on duplicated-thresholds
Fix: thresholds set in global l… (compare)
cizezsy on duplicated-thresholds
Fix: thresholds set in global l… (compare)
cizezsy on dev
remove unused import (compare)
cizezsy on dev
Fix: threshold cannot be serial… Merge pull request #66 from jen… (compare)
cizezsy on threshold-serialize
Fix: threshold cannot be serial… (compare)
I'm currently in the progress of improving the user interface of the Coverage plugin (see jenkinsci/code-coverage-api-plugin#203 for details). The basic idea is to improve the navigation so that only two clicks are required to see the actual coverage view for the source files. Additionally, I am reusing some ideas from my warnings plugin: font awesome icons, coverage trend chart, Bootstrap 5 cards in the detail view, table view for fast source code access, responsive design, etc.
I am also trying to refactor the code base so that in future release we will be able to create delta coverage results for individual elements. That means that we will not only see the changed coverage (as project total) of a pull request but also the coverage of the changed or added lines in a pull request. Using this information we can highlight lines without coverage in pull requests using the GitHub checks API.
The work is still in progress but it might be helpful to get some comments as early as possible. So a simple question: am I on the right way or am I removing or changing some important features? What is also not clear for me from the code base and the existing issues, how are you typically using the plugin?
publishCoverage
step or are you calling the coverage step multiple times? In the latter case it is not clear for me how we can create delta reports in the future, since the delta changes with every invocation. configure the reference job
ThresholdTarget
? I want my threshold to be against total number of lines covered. Is this supported?
I am a bit confused because I'm not sure what the "mergeToOneReport" option does (since there can only be a report, it's always "merged" isn't it?), and because in the Jenkins job page I get:
Coverage Report
Project Coverage:
Line: 14.02%
Branch: 14.86%
What's the point of having that "Project Coverage" if there can be only one project?
I suspect I'm missing something. FWIW I'm using the coberturaAdapter with a xml file created by gcovr.
Hi,
i am about to setup the code-coverage-api-plugin for a java maven project (jacoco) and wanted to define some thresholds like:
[thresholdTarget: 'Branch', unhealthyThreshold: 65.0, unstableThreshold: 75.0]
This gives me and NPE when running on Jenkins, as the target "Branch" seems not to exist. It works fine with e.g. "Line".
I could not find the correct target name for branch coverage, could someone give me a hint, how to setup the thresholds for branch coverage?
Best & Thanks