jenkinsci/code-coverage-api-plugin

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.

You can build the plugin manually and install in a test instance.

Cristian Morales Vega

@RedDwarf82_gitlab

Warnings NG has the "id" and "name" options so I can have multiple reports in both the Jenkins job page and in the GitHub reports.

That's not possible with publishCoverage, right?

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.

Cristian Morales Vega

@RedDwarf82_gitlab

FWIW at some point I tried to do

publishCoverage ...
withChecks('Different coverage') {
  publishCoverage ...
}

And it didn't go well, GitHub was saying that it never received all the Checks.

Ulli Hafner

@uhafner:matrix.org

[m]

This part of the plug-in is currently broken, see corresponding issue

Cristian Morales Vega

@RedDwarf82_gitlab

jenkinsci/code-coverage-api-plugin#236, I see.

Where communities thrive

People

Repo info

Activity