Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 25 2019 06:05
  • Jan 23 2019 13:32

    cizezsy on dev

    [maven-release-plugin] prepare … (compare)

  • Jan 23 2019 13:32

    cizezsy on code-coverage-api-1.0.7

    (compare)

  • Jan 23 2019 13:32

    cizezsy on dev

    [maven-release-plugin] prepare … (compare)

  • Jan 23 2019 13:24

    cizezsy on dev

    Fix: thresholds set in global l… Merge pull request #67 from jen… (compare)

  • Jan 23 2019 13:24
    cizezsy closed #67
  • Jan 23 2019 07:09
    cizezsy synchronize #67
  • Jan 23 2019 07:09

    cizezsy on duplicated-thresholds

    Fix: thresholds set in global l… (compare)

  • Jan 23 2019 07:06
    cizezsy reopened #67
  • Jan 23 2019 07:06
    cizezsy closed #67
  • Jan 23 2019 07:03
    cizezsy opened #67
  • Jan 23 2019 07:02

    cizezsy on duplicated-thresholds

    Fix: thresholds set in global l… (compare)

  • Jan 23 2019 03:31

    cizezsy on dev

    remove unused import (compare)

  • Jan 22 2019 09:46

    cizezsy on dev

    Fix: threshold cannot be serial… Merge pull request #66 from jen… (compare)

  • Jan 22 2019 09:46
    cizezsy closed #66
  • Jan 22 2019 09:31
    cizezsy opened #66
  • Jan 22 2019 09:30

    cizezsy on threshold-serialize

    Fix: threshold cannot be serial… (compare)

  • Jan 18 2019 03:48
    cizezsy commented #65
  • Jan 17 2019 18:08
    andre2007 opened #65
  • Jan 17 2019 12:35
    cizezsy closed #64
Sagar Khurana
@hellosagar
yes I read the pluin doc
in doc this is written This plugin serves as API to integrate and publish multiple coverage report types.
idk after reading this what is use of this plugin
sorry if my question quite noob level
Ullrich Hafner
@uhafner

This means that the plugin can be used by other plugins that want to publish a test report. Then the main functionality can be reused, just a parser for the test coverage results need to be provided. But you can also use this plugin in a standalone way: if your coverage reports are in the jacoco format.

What are you planning to do?

Sagar Khurana
@hellosagar
@uhafner I have to explore how can I extract REST endpoint from the plugin so that later on I can get the Open API specification and then generating the documentation using the Open API Specification
but I dont know how this lugin works
what do you suggest me for this
Ullrich Hafner
@uhafner
Do you already have a Jenkins instance running with the plugin? You need to run a job that computes the code coverage. Example: https://ci.jenkins.io/job/Plugins/job/warnings-ng-plugin/job/master/1141/coverage/
Sagar Khurana
@hellosagar
oh Okay so for that I have to make a sample project and run test for that code and this plugin is going to give me the Visualisation for how my code is performing?
is it?
Ullrich Hafner
@uhafner
Yes, the code coverage plugin shows the results of the coverage… You can also see an example in action if you run the docker Jenkins in https://github.com/uhafner/warnings-ng-plugin-devenv
Sagar Khurana
@hellosagar
oh okay
and that link you shared is containerised using Docker and using Jenkins and you mean I should look into your plugin who its interegrated with Code coverage
Ullrich Hafner
@uhafner
Sorry, forget the last link. Seem that I removed the coverage part recently.
Sagar Khurana
@hellosagar
oh okay
currently Im looking at this https://www.youtube.com/watch?v=BdbsZ4Z5jIE
Hope this helpful
If you have any helpful link that also would be great 🙂
Ullrich Hafner
@uhafner
Yes, the video is helpful!
Sagar Khurana
@hellosagar
okay lme finish it
Ullrich Hafner
@uhafner
You can also clone https://github.com/uhafner/codingstyle and run jenkins.sh. This will run Jenkins in Docker and provides a project that has compile results, test results, coverage, etc.
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
image.png
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
image.png
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