jenkinsci/code-coverage-api-plugin

Sagar Khurana

@hellosagar

oh okay yeah Let me try this also
Hopfeully with this I get a demontration on how to use Code Coverage plugin
Thanks

Sean Brennan

@sbrennan4

Hi! I'm running this plugin as in a scripted pipeline as described by the example given, publishCoverage adapters: [jacocoAdapter('target/site/jacoco/jacoco.xml')], and getting an error

Archiving artifacts
‘[adapters:[@jacocoAdapter(<anonymous>=target/site/jacoco/jacoco.xml)]]/*.*’ doesn’t match anything, but ‘*.*’ does. Perhaps that’s what you mean?
ERROR: No artifacts found that match the file pattern "[adapters:[@jacocoAdapter(<anonymous>=target/site/jacoco/jacoco.xml)]]/*.*". Configuration error?

any suggestions?

Ulli Hafner

@uhafner:matrix.org

[m]

Are you archiving artifacts one line above that code in your Jenkinsfile? It seems that that line of code is part of the previous step.

Sean Brennan

@sbrennan4

Ah I found the issue. One of our shared libraries is defining a custom step with the same name of publishCoverage.

Oleg Nenashev

@oleg-nenashev

Thanks all for the great plugin! Had a presentation about Advanced Code Coverage in Jenkins today with overview of Code Coverage API and GitHub Checks integrations. Was happy to present our GSoC and to do live demos from ci.jenkins.io. https://twitter.com/oleg_nenashev/status/1400524585464963074

Dinesh

@fargonmer

how do we get cucumber data from jenkins. Does Jenkins provide API for exporting data to external website (like JAcoco)

Ulli Hafner

@uhafner:matrix.org

[m]

There is a plugin for cucumber, did you try that? (https://plugins.jenkins.io/cucumber-reports/)

Dinesh

@fargonmer

i did tried that

I can able to generate the reports in Jenkins Pieplines.

But how to get that cucumber.json file from Jenkins and feed it to an external website.

Ulli Hafner

@uhafner:matrix.org

[m]

There are other plugins that can copy artifacts to different end point. You will get some answers in the main Jenkins channel

Dinesh

@fargonmer

https://plugins.jenkins.io/cucumber-reports/ I did saw in the main jenkins channel

doesnt find any

Ullrich Hafner

@uhafner

Release 1.4.0 is available now: it provides support for the new pull-request-monitoring-plugin.

Ullrich Hafner

@uhafner

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?

Are you using a single 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.
Are you using the heat map that shows the hierarchy of the coverage? Or would it be helpful if we remove that part totally (or replace it with a tree map or sunburst diagram)?
Are you using the aggregation with a tag? Or rephrased: how should the ideal coverage hierarchy look like? Project, Package, File, Class, Method and then Line and Branch as leaf nodes?

rompic

@rompic

Hi, we are calling publishCoverage twice in a pipeline (without the tag) and that seemed to work until recently. (two coverage reports were available below the same menu item). after updating it seems to be overwritten.
Is that expected?

2 replies

rompic

@rompic

I also just noticed that the top level link (on job level not build level) seems to be wrong a multi-branch pipeline setup

1 reply

rompic

@rompic

I will try adding the tag, but from the readme it is not really clear to me how it should behave in both scenarios

1 reply

rompic

@rompic

it used to look like this^^

which is nice because we have both coverage reports available (alternatively having two named coverage items on the left side of the job would be ok as well)

now they are overwritting each other and i only see the second coverage report

Ulli Hafner

@uhafner:matrix.org

[m]

I see. Showing the results of two different projects in a single page seems to be hard from the UI design. In the new details view there is much more information visible in one page. I wonder if it would be simpler to implement if we use the same pattern as in the warnings plugin: different toplevel links that show the individual results. (Maybe that actually is the reason for the tag. Maybe we just need to transform the tag to an id, so that we also have the tag in the URL.

Can you please create a new issue?

rompic

@rompic

sure. thanks for the fast response

rompic

@rompic

I'll play around a little bit with the tags before creating the ticket

Oluwole Oyetoke

@OluwoleOyetoke

Does anyone how to resolve this error:

"Found no reference build, won't calculate coverage diff"

The Jenkins job fails after this error.

Oluwole Oyetoke

@OluwoleOyetoke

Do I need to merged first and this will correct itself from the next PR?

Ulli Hafner

@uhafner:matrix.org

[m]

The failure of your job is not be related to the message. The message simply says that you did not correctly configure the reference job. How do you invoke the step? Did you configure the reference build before the coverage?

Oluwole Oyetoke

@OluwoleOyetoke

I called publishCoverage adapters: [jacocoAdapter('target/site/jacoco/jacoco.xml')] after build.

What do you mean by configure the reference job

Ulli Hafner

@uhafner:matrix.org

[m]

https://github.com/jenkinsci/git-forensics-plugin#reference-build

Example: https://github.com/uhafner/codingstyle/blob/6b7276339f5c99a92f1cce53c402582772c7ecf2/Jenkinsfile#L7

Oluwole Oyetoke

@OluwoleOyetoke

Thanks, that fixed it.

Is there any documentation on ThresholdTarget? I want my threshold to be against total number of lines covered. Is this supported?

Oluwole Oyetoke

@OluwoleOyetoke

Is there a reason why line and instruction coverage will decrease for a PR where I only made changes to pom.xml?

Oluwole Oyetoke

@OluwoleOyetoke

I replay the same job and sometimes line coverage diff is 0%, other times its -0.0086%

Without any change in code

I'm wondering why this is happening

Ulli Hafner

@uhafner:matrix.org

[m]

This is not supported. Here are some values: https://github.com/jenkinsci/code-coverage-api-plugin/blob/master/src/main/java/io/jenkins/plugins/coverage/model/CoverageMetric.java

It is always a percentage.

I think the delta computation currently has a rounding problem.

See jenkinsci/code-coverage-api-plugin#286

ayli

@ayli:matrix.org

[m]

Is it possible to speed up the copying of the source code or attach code without copying it? Currently I have 5800 files and it spends 1 hour. My call publishCoverage adapters: [jacocoAdapter('**/target/site/jacoco/jacoco.xml')], sourceFileResolver: sourceFiles('STORE_LAST_BUILD')

ayli

@ayli:matrix.org

[m]

Ah I see improvement jenkinsci/code-coverage-api-plugin#310. But it was not released yet?

Ulli Hafner

@uhafner:matrix.org

[m]

Yes, this PR (and some others) are feature complete and will be released soon. If you are interested in testing, please let me know!

Currently the UI is not so good on small displays so I want to fix that before a next release.

Where communities thrive

People

Repo info

Activity