This indicates that there are coverage numbers for a class with identical
name, but different code, which confuses the plugin, either exclude those
classes completely or ensure that only one is covered during test runs.
Could also be some recompilation during test-runs or not cleaning an old
.exec
Sorry for the late reply, but I think you are better off discussing
this on the jacoco discussion group, see
http://www.eclemma.org/support.html for details.
It may even be fixed in the latest version of JaCoCo (0.7.1), I think
I remember previous discussions about similar problems with the Maven
co plugin use (0.7.1) ?
>
>
> On Sun, Aug 3, 2014 at 10:00 AM, Dominik Stadler <
> dominik.stad...@gmail.com> wrote:
>
>> Sorry for the late reply, but I think you are better off discussing
>> this on the jacoco discussion group, see
>> http://www.eclemma.org/
Hi,
in Jenkins, jobs are separated, so you can not access stuff from one
in another, either make sure the source code is checked out in your
2nd job as well somehow or the 1st job creates artifacts of the
sourcecode which the 2nd job imports.
The JaCoCo plugin in Jenkins can handle integration te
Hi,
yes, this is a flaw in the way the plugin is implemented currently, it
needs to re-compute the data on each access to one of the coverage-screens,
https://issues.jenkins-ci.org/browse/JENKINS-16010 is another effect of it.
There is likely no easy way to "fix" this other than change how the plu
6:42 PM, Chinthaka Chandrasekara
wrote:
> Thanks for the reply. I tried what you have said but it ultimately shows a
> code coverage of zero when running the automation tests against the
> development code.
>
> On Saturday, September 13, 2014 8:45:45 PM UTC+5:30, Dominik Sta
ll be a bit incorrect if some of the
> past builds are removed, but in general it will show correct trend.
>
> Guys, what do you think about these improvements? Should I create a pull
> request for them?
>
>
> Thanks,
> Alex
>
>
> On Saturday, September 13, 2014 6:16
Hi,
There is currently no license mentioned in the jacoco-plugin, I looked
at other plugins, most use the MIT license, any objection to adding
this to the pom.xml the same way that the subversion-plugin does? See
https://github.com/jenkinsci/subversion-plugin/blob/master/pom.xml
Thanks... Dominik
0,
> maxComplexity=0]
> [JaCoCo plugin] Publishing the results..
> [JaCoCo plugin] Loading packages..
> [JaCoCo plugin] Done.
> Finished: SUCCESS
>
>
> On Tuesday, September 16, 2014 12:31:26 AM UTC+5:30, Dominik Stadler wrote:
>>
>> The plugin prints out some of
. I haven't used Ant before and I am not
> familiar with getting the Jacoco code coverage manually (outside of Jenkins)
> using the Maven plugin. Could you run me through the basic steps in order to
> achieve this? Thanks in advance.
>
> On Thursday, September 18, 2014 3:14:34 AM UT
Hi,
I think you are better off asking questions related to JaCoCo itself
like this and the next one directly on the JaCoCo forums, see
http://www.eclemma.org/jacoco/, we are also more or less just users of
JaCoCo and do not know many of it's internals.
Thanks... Dominik.
2014-09-30 14:18 GMT+02:
Hi Ognjen,
any chance of rolling release 1.0.17 of the jacoco-plugin soon? We get
a number of duplicated JIRA entries because of bugs that are fixed on
HEAD, but not in 1.0.16, especially the broken link in the
view-column...
Dominik.
--
Azért kapta ezt az üzenetet, mert feliratkozott a Google
ll be necessary...
Dominik.
2014-11-24 22:23 GMT+01:00 Ognjen Bubalo :
> Hi,
>
> Sorry for being away from the project. I will check how can I give you
> access to do the release.
>
> I made the release 1.0.17. Should be available soon.
>
> Thanks a lot,
> Ogi
>
&
.
Whom do we need to contact to get me access there?
Dominik.
On Wed, Nov 26, 2014 at 5:17 PM, Dominik Stadler
wrote:
> Hi,
>
> thanks, yes, would be nice, I have an account on jenkins-ci, the pages
> at
> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins
Hi,
Can you post the last few lines of log-output of the jenkins job where
the jacoco plugin notes down which settings it uses and which matches
are found, hopefully this allows us to see why it fails to read the
file for you.
Dominik.
On Tue, Jan 6, 2015 at 10:39 AM, Matt Geis wrote:
> I've ha
Hi,
I would probably not use the JaCoCo Jenkins Plugin for this, but
rather look at JaCoCo itself and the types of reports it can produce,
see task report in http://www.eclemma.org/jacoco/trunk/doc/ant.html,
as the JaCoCo plugin depends on the results from JaCoCo itself, it is
probably easier to
The main two pieces of the plugin are the build-time processing and
additional processing later when data is viewed in Jenkins.
During building JaCoCo runs as post-build action and will collect the
.exec file together with classes and sources and will store all those
things as part of the build-in
Hi,
for the class directories you should only list the parent directory
where underneath the Java packages are stored, i.e. for
build/classes/com/example/App.class, you would have build/classes.
Is that the case here?
Dominik.,
On Tue, Apr 28, 2015 at 4:46 PM, Eoin Byrne wrote:
> Some info I f
Hi,
I think you are looking for JaCoCoBuildAction.getResult() which is
called both at the end of the build but also when the coverage report
is requested for a build.
Dominik.
On Sat, May 23, 2015 at 8:47 PM, abhishek gupta wrote:
> Hi,
> I want to do check coverage of newly added
lexity=0]
> [JaCoCo plugin] Publishing the results..
> [JaCoCo plugin] Loading packages..
> [JaCoCo plugin] Done.
>
>
>
>
> On Thursday, January 8, 2015 at 6:41:03 AM UTC-5, Dominik Stadler wrote:
>>
>> Hi,
>>
>> Can you post the last few lines of log-output of t
On Wednesday, May 27, 2015 at 3:36:53 PM UTC-4, Dominik Stadler wrote:
>>
>> Hmm, that looks fine on a quick glance as long as the class and source
>> files are available in those directories and the class-files actually
>> match the ones that are used while recording the c
ugin] Loading inclusions files..
>>> [JaCoCo plugin] inclusions: [**/*.class]
>>> [JaCoCo plugin] exclusions: [**/*Test.class]
>>> [JaCoCo plugin] Thresholds: JacocoHealthReportThresholds [minClass=0,
>>> maxClass=0, minMethod=0, maxMethod=0, minLine
I would run JaCoCo as part of the build-steps, i.e. in the Gradle or
Ant build itself and then just send out the resulting JaCoCo report
files as attachment, without actually requiring JaCoCo plugin.
Email-Ext can also include the contents of the report files via the
${FILE, ..} statement, see e.g
The only thing that I can think of based on your description is that
you had an older jacoco.exec binary file selected in jenkins compared
to what the build results, so the resulting report in jenkins may be
based on unrelated/old coverage data?
Dominik.
On Thu, Jun 11, 2015 at 7:15 PM, abhishek
Ok, thanks for the note, I did not think of this, good to know!
Dominik
Am 19.06.2015 19:56 schrieb "abhishek gupta" :
> Reason for this , I was using old version of plugin, after upgrading it to
> latest pluging solve the issue. In latest pluging it is using latest
> version jacoco core
> 0.7.4.
Hi,
you would likely need to collect the information into separate
jacoco.exec files already while running tests or at least create
different "sessions" in the binary file so that the raw coverage data
is in per-test form already. Then you would need to correlate these
sessions to the actual tests
he a
> second export ? If not, I'd object against using this format, because there
> is a loss of information.
>
> Experiments done with jacoco 0.7.4
>
> Am Freitag, 10. Juli 2015 11:07:38 UTC+2 schrieb Dominik Stadler:
>>
>> Hi,
>>
>> you would likely
Hi,
When the plugin is running via a Job, it can also run on a remote
build-slave and will transfer data to the server accordingly. There is no
additional functionality to provide "server" for collecting build data, but
you can probably easily build a simple job (via shell-script build actions
whi
the report will show the coverage collected from
> multiple sources of exection data.
>
> 2016-02-01 21:02 GMT+01:00 Dominik Stadler :
>
>> Hi,
>>
>> When the plugin is running via a Job, it can also run on a remote
>> build-slave and will transfer data t
Ok, thanks for the note. I was about to suggest to check versions!
Dominik
Am 23.02.2016 21:10 schrieb "Patrick Ewing" :
> Update: Disregard above, I found the issue when I double checked the
> versions of everything. The JaCoCo jars were 0.7.4. Upgrading to 0.7.5
> resolved the problem.
>
> --
>
What version of the jacoco-plugin are you using? Please try with 2.0.0 or
newer.
Thanks... Dominik
Am 05.03.2016 01:34 schrieb "sahana tambi" :
> I am using the following script for jacoco code coverage. HTML reports
> display correct results for junit test cases, where as the exec file shows
> 0
:
> Yes, I am using 2.0.1 version. But no luck, how do I open an exec other
> than jenkins. So that i know that jenkins jacoco plugin is the issue and
> not jacoco code coverage itself.
>
> On Friday, March 4, 2016 at 11:56:15 PM UTC-8, Dominik Stadler wrote:
>>
>> What versi
rocessDemoDebugJavaRes UP-TO-DATE
> :app:processDemoDebugUnitTestJavaRes UP-TO-DATE
> :app:compileDemoDebugUnitTestSources
> :app:mockableAndroidJar
> :app:assembleDemoDebugUnitTest
> :app:testDemoDebugUnitTest
> :app:testDemoDebugUnitTestCoverage
>
> BUILD SUCCESSFUL
>
&g
..
> [JaCoCo plugin] Loading packages..
> [JaCoCo plugin] Done.
> Run condition [Always] enabling perform for step [[Delete workspace when
> build is done]]
>
> Deleting project workspace...
> done
>
> Notifying upstream projects of job completion
> Finished: SUCCESS
>
you likely
actually run a plugin-version below 2.0.0 which can not work with JaCoCo
0.7.5 or newer.
Dominik.
On Tue, Mar 8, 2016 at 2:48 PM, Dominik Stadler
wrote:
> Hmm,
>
> that looks fine on a quick look, not sure why you end with no results,
> looks a bit like the .exec files
tambi
wrote:
> That's a good catch! How do I verify the plugin version on Jenkins? How do
> I use latest jacoco plugin in jenkins? Or is it required for me to user
> older version of Jacoco than 0.7.5? If so which version of jacoco should I
> use?
>
> On Tue, Mar 8, 2016 at 6:25 A
Please ensure you use the latest version of JaCoCo-plugin which is version
2.0.1 and a JaCoCo version of at least 0.7.5, there have been issues like
this in v. 2.0.0.
Dominik.
On Wed, Mar 9, 2016 at 7:28 AM, suneetika chaudhary
wrote:
> Hi,
>
> I also used jacoco to create report,
> for me also
Hi,
There is a PullRequest being discussed which I think is related to that,
but as I don't know much about the workflow/pipeline stuff in Jenkins I
cannot state if that is what you are looking for...
See https://github.com/jenkinsci/jacoco-plugin/pull/66
Unfortunately the PR is waiting for a re
The message might be a follow-up because it did not copy any .class files
before.
Can you post all log output of the jacoco-plugin in the Jenkins build
output and also state which exact version of the jacoco-plugin this is?
Thanks... Dominik.
On Mon, May 23, 2016 at 10:07 AM, Matt Turner
wrote:
Unfortunately not, there was some discussion around this when the
exec-binary-format changed in an incompatible way a while ago and I tried
to have a go but I ran into trouble supporting all the things the plugin
does currently so I did not pursue it further at that time.
I have these changes stor
Can you post all the relevant output from the jenkins run? It sounds like
the configured location does not match the actual file location.
Dominik
On Aug 30, 2016 7:23 PM, "Nishanth Prakash"
wrote:
> I am currently using Jacoco 0.7.7 with Jacoco plugin version 2.0.1. I have
> also attached the
That is actually the output of the maven build itself, not the
jacoco-plugin in jenkins. It seems somehow your maven project is not set up
for code coverage correctly, but I am not sure what the issue is based on
the given information.
I would first ensure that code coberage is computed correctly
Hi,
there is currently no way to configure this in the plugin, if you provide a
pull request which adds this as a configuration we should be able to
include this in the future.
Dominik.
2016-09-09 17:21 GMT+02:00 James Kojo :
> Is there a way to configure the plugin to show a stack graph instea
Hi,
the jacoco.exec needs to be created in your build-script, only then the
plugin can prpovide values. Usually looking at the build-log shows what
happened, the jacoco-plugin will include some information about it's state
there.
Dominik
2016-10-06 20:21 GMT+02:00 sneha agarwal :
> Hi ,
> I am
eCoverage/taxmaster/tax-service/src/test/java/com/myntra/taxmaster/util
>
> /data/jenkins/workspace/TaxMasterServiceCodeCoverage/taxmaster/tax-service/src/test/resources
> [JaCoCo plugin] Loading inclusions files..
> [JaCoCo plugin] inclusions: []
> [JaCoCo plugin] exclusions: []
&g
erage/taxmaster/tax-service/src/main/webapp
>>>
>>> /data/jenkins/workspace/TaxMasterServiceCodeCoverage/taxmaster/tax-service/src/main/webapp/META-INF
>>>
>>> /data/jenkins/workspace/TaxMasterServiceCodeCoverage/taxmaster/tax-service/src/main/webapp/
Hi,
You can look for the string "Overall Coverage Summary" in Github
https://github.com/jenkinsci/jacoco-plugin/search?utf8=%E2%9C%93&q=Overall+coverage+summary,
from there you will find this file:
https://github.com/jenkinsci/jacoco-plugin/blob/0d29b78e60a21296ae92f66cb01132d9fe70ac7b/src/main/re
Hi,
you will need to provide the correct path, according to the directory
layout, the .class files are under build/classes/test, but you provided
"packages/arp/src/".
You could also try to set the class-include to only build/classes/src, then
the tests would not be included in the first place, ma
not sure what the issue is as I do not know you project-layout. But you can
try a very broad inclusion via "**/*.class" and then exclude anything on a
similar broad pattern "**/*Test.class".
Thanks... Dominik.
2016-11-29 15:55 GMT+01:00 Frank fan :
> when write the include is packages/arp/src/
Hi,
Any reason why you are not using the latest version of the plugin?
The github project and the wiki-page state that since JaCoCo 0.7.5, version
2.0.0 or higher of the plugin is needed, did you try?
Regards... Dominik.
2016-12-03 20:03 GMT+01:00 Anwar Haque :
> Also to add its a gradle buil
Not sure if there is some protection against such access from one project
to another project in Jenkins, the plugin does not do anything special,
just resolves the pathes to actual matching files/folders. However it is
anyway dangerous and hard to maintain to have such an access, especially if
the
I think you need to discuss this on the jacoco discussion area and please
also provide more info about your actual setup, buildsystem, ...
Dominik
On Feb 22, 2017 08:01, "sneha agarwal" wrote:
>
> Hi,
> I have multiple services on same server and I need to capture the code
> coverage for each
I don't know the jenkins internals that are involved in multi-module builds
well, but there is no specific code to handle this in the jacoco-plugin
itself as far as I see.
Dominik
On Mar 5, 2017 11:06 AM, "Martin Hoerning"
wrote:
> Hi,
>
> I have a Multi-Module (~100 modules) maven-build and us
This is currently not supported, you can however collect coverage for the
two combined. The only other option that I see would be to use two separate
jobs that run the two sets of tests separately.
Dominik
On Mar 7, 2017 16:15, "Manoj" wrote:
> Hi,
>We have JaCoCo plugin in our Jenkins. We
Can you provide the full build-log from jenkins, at least the part where
the jacoco-plugin performs it's work? And how does the configuration of the
jacoco-plugin your job look like?
Thanks... Dominik.
On Sat, Jun 24, 2017 at 4:50 AM, Steve Wardell
wrote:
> I'm running an older version, 1.0.16,
jacoco-maven-plugin
>
> ${jacoco.version}
>
>
>
>
>
> pre-unit-test
>
>
>
> prepare-agent
100,
> branch: 100, instruction: 100
>
>
> So a few questions:
>
>
> 1. Why does it not say it finds the exec file? Does it need to also
>find the classes and/or source at the same time to load?
>2. Why don't the directories get created for jacoco/classe
Wardell
wrote:
> Unfortunately, same behavior. Good idea to try though. Thanks! Any way to
> all more debug logging?
>
> On Sun, Jul 2, 2017 at 4:31 AM Dominik Stadler
> wrote:
>
>> Hi,
>>
>> Can you try **/*.exec instead of **/**.exec?
>>
>> Domi
Hi,
the plugin is pretty tied to the .exec format, we discussed switching to
the XML report at some point, but it was a large amount of work and I did
not find all the information that the plugin uses in the XML. JaCoCo itself
also does not provide functionality to read back in the information fro
t could I could write to, if I had the raw
> coverage data?
>
>
> On Wednesday, 19 July 2017 16:36:10 UTC-4, Dominik Stadler wrote:
>>
>> Hi,
>>
>> the plugin is pretty tied to the .exec format, we discussed switching to
>> the XML report at some point, but it w
ch 15, 2016 at 10:44:18 AM UTC-7, sahana tambi wrote:
>>
>> Thanks a lot Dominik! I am able to get the reports working with Jacoco
>> plugin. Upgradig the plugin version fixed my problem.
>>
>> On Wed, Mar 9, 2016 at 12:08 AM, Dominik Stadler
>> wrote:
>>
I don't know of a way to do this currently, this would likely require
enhancements to the plugin, but would probably not be too hard to implement.
Dominik
On Jul 27, 2017 05:04, "Praveen Maurya" wrote:
> I have classes bundled into different jar, at IT(integration tests are )
> phase, the serv
Please note that this list is mainly for discussion of the jacoco-plugin
for jenkins, not jacoco itself. there are other channels available for
jacoco itself where people with more in-depth knowledge will look at your
question.
>From a high level your problem sounds like you are using reflection t
Hi,
The delta-thresholds are computed based on the last successful build
compared to the current build. So you can remove the previous successful
builds or lower the thresholds to allow the current build to succeed before
raising the thresholds again. It could also work if you disable the
threshol
Hi,
It seems you set deltaComplexity to 0.0 so you make the build fail as soon
as this value is smaller at all and the build reported a change of 0.1698
less, so it is set to failed accordingly.
Dominik.
On Mon, Sep 11, 2017 at 4:27 PM, david linse wrote:
>
> i have another question regarding
is some room to make more clear in the log, which of the
> metrics caused the build to fail .. ?
> are there any plans to configure an 'mark as unstable' option for the
> thresholds value ?
>
> kind regards
> ~david
>
> Am Montag, 11. September 2017 17:42:38 UTC+2
Hi,
this is currently not possible, the jacoco-plugin expects to produce one
report only. Maybe you can do something like this by using separate
downstream-jobs which access the same workspace or by producing the
jacoco-reports in an ant-build.xml or Gradle build which is called by the
Jenkins job
Hi,
It most likely depends on the version of the Jenkins base-version that the
plugin still tries to support. If that version of Jenkins still supports
Java 7, then we could only get rid of it by upgrading to a newer Jenkins
base-level.
Unfortunately I am too less involved with Jenkins nowadays t
I'm ready to help.
> My goal is to gain knowledge of the plugin in order to fix
> https://issues.jenkins-ci.org/browse/JENKINS-36168, as it's a real
> problem for me.
> Vincent
>
> Le mardi 14 novembre 2017 23:33:42 UTC+1, Dominik Stadler a écrit :
>>
>> H
Hi,
please try without the leading **/, i.e. com/module/package/**, as
otherwise it might indicate "at least some package names before com/...
which you won't have.
Dominik.
On Thu, Nov 23, 2017 at 11:19 AM, Rajdeep Biswas
wrote:
> Hi,
>
> I am trying to exclude some packages and classes from
> LTS releases of Jenkins now require Java 8, so if you're OK I'm going to
> drop Java 7 support in my PR.
>
> 2017-11-23 17:46 GMT+01:00 Dominik Stadler :
>
>> Bringing the related PR into shape and testing it would be a good start
>> IMO. Progress stalled on
Jup, seems there are newer versions available, PR welcome!
Dominik.
On Tue, Feb 6, 2018 at 11:02 AM, Lars Grefer wrote:
> The jacoco version used by the jenkins-plugin is too old.
>
> Am Dienstag, 19. Dezember 2017 16:32:28 UTC+1 schrieb Emanuel Hategan:
>>
>> Hi there,
>>
>> I'm using the jaco
Hi,
the note on top of the main wiki page for the plugin tries to define
required versions, see https://wiki.jenkins.io/display/JENKINS/JaCoCo+Plugin
Dominik.
2018-04-11 20:01 GMT+02:00 aswak sk :
> Hi,
> I was looking for information on which jacoco plugin is compatible with
> which Jenkins ve
Hi,
Make sure that the plugin is actually installed, i.e. via "Manage Jenkins"
-> "Manage Plugins" -> "Installed"
If that does not help, please post the full jenkins log to let us check for
startup issues.
Dominik.
2018-04-24 14:31 GMT+02:00 :
> Hi all,
>
> Im using jenkins ver 2.117 and have
Unfortunately not much experience with Java 10 on my side and also not much
time to invest...
I tried quickly, but failed to even compile using Java 10 with various
errors, after some plugin-updates it fails with more errors, all related to
Java 9/10 support in various used parts, e.g. Jenkins, Ma
Hi,
I would use the jacoco plugin of the buildsystem that you are using for
generating such a report without the jenkins plugin being involved at all.
Ant/Maven/Gradle all can integrate JaCoCo and generate html-reports that
you can then publish out of the build-results.
Dominik.
On Fri, Aug 17,
Hi,
it's hard to tell from the description, I would take a look at the full log
of the job. It contains information if the exec-file was found and other
information from the plugin.
Dominik.
On Thu, Nov 8, 2018 at 10:05 AM Malshani Senarathne <
pamoda.malsh...@gmail.com> wrote:
> Hi,
>
> I nee
Hi,
I will review and merge changes if you want to contribute something like
that. Just send a PR and I should respond in a week or two. Please try to
get some coverage of new code and make sure that the default behavior is
not changed, i.e. new features need to be activated/configured via
additio
Both Jenkins and Jacoco-plugin have a much newer version (JaCoCo-plugin
3.0.4 requires Jenkins 2.54 or newer) which contain numerous bug-fixes, so
you probably should verify with a more recent version if the problem still
exists there.
Dominik.
On Mon, Mar 11, 2019 at 9:07 AM yash sharma wrote:
The plugin uses simple unit-tests, see
https://github.com/jenkinsci/jacoco-plugin/tree/master/src/test/java/hudson/plugins
No integration-style tests for now, probably because none of the few
committers knew enough and/or because of the additional effort it would be
to keep them stable/running ove
Can't see that in a local run, are you sure this is coming from the plugin
and not from your build-system?
Note: All lines printed by the plugin are prefixed with "[JaCoCo plugin]"
Can you show some of the output?
Also which version of jacoco-plugin do you use?
Thanks... Dominik.
On Wed, Dec 1
according to the stacktrace, Jacoco itself, when called from the jenkins
plugin, cannot read the coverage data of the build, so it looks like your
.exec file is somehow corrupted or resulting from a build with an older
version of jacoco.
Dominik
On Sat, Jan 11, 2020, 20:19 devops tutorials
wrote
Hi,
On License: it uses the MIT License, see the pom.xml. We probably should
state that a bit more clearly in the README.
On Contributing: Would be very welcome as there is only one maintainer (me)
and I am very mostly inactive as well.
Let me know if you need some technical insight into how the
What is the actual error message?
D.
On Thu, 20 Aug 2020, 12:21 Allison Johnston,
wrote:
> Hi, we have just upgraded to jacocoPublisher 3.0.7, but when we try to use
> it with Kotlin-classes we're getting an error
>
> While reading class directory: /builds/121/jacoco/classes
>
> Is there someth
Please provide the full output from the job-run.
D.
On Thu, 20 Aug 2020, 12:58 Allison Johnston,
wrote:
> thats the only message we get. Our jenkins script fails at this point and
> it only happens when we include **/kotlin-classes on the
> classPattern: '**/classes,**/kotlin-classes'
> if we j
The JaCoCo Jenkins Plugin does not target this use-case currently. But as
you run jacoco as part of your build-system already, the easiest is to
configure the proper report as part of your build and export it as part of
the Jenkins configuration as "artifact" of the build. E.g .the XML report
is th
Hi,
the plugin is mostly lacking a few more active maintainers to get more
frequent releases. So the best option to speed up things in the long run
would be to come on board and help a bit by reviewing JIRA issues and PRs,
keeping things updated and do the release-work from time to time. Would be
Cool,
The README should describe most of the usual "how to contribute" things
already. I'd say you should get used to the code a bit via one or two PRs
before requesting more permissions.
I will write up a new chapter about "how to release", pointing mostly to
https://wiki.jenkins.io/display/JENK
Hi,
I have now released version 3.1.1 with the changes to the log-output.
Also up-to-date information about how to contribute and help with releases
is now available at
https://github.com/jenkinsci/jacoco-plugin/blob/master/README.md
Thanks... Dominik.
On Wed, Jan 13, 2021 at 3:22 PM pulg...@g
Hi,
this group is solely for questions around usage of the jacoco-plugin in
Jenkins. As your question seem to be more related to using jacoco itself,
you will likely get better answers if you contact the JaCoCo community
instead.
Regards... Dominik.
On Wed, Mar 3, 2021 at 2:42 PM sai kumar wrot
Hi,
currently these settings have to be duplicated in the build-config as the
plugin does not know about how the various build-systems configure these
settings.
Dominik.
On Thu, Nov 4, 2021 at 11:52 PM 'Scott Shipp' via Jenkins JaCoCo plugin
mailing list wrote:
> I am asking if the exclusions
Thanks for the suggestions, unfortunately the plugin is pretty much in
"maintainance mode" at the moment, but PRs with new features are highly
welcome, just make sure to not break existing functionality, maybe by
adding a new option "read configuration from pom.xml" that is not enabled
by default.
Hi,
this sounds like a question for the JaCoCo code coverage functionality
itself. This is not handled here, as this list mostly focusses on the
Jenkins plugin for including JaCoCo results in build results. You will get
better answers if you contact the JaCoCo developers directly or ask via
stacko
Hi,
This plugin allow to visualize coverage data for Jenkins Jobs. It should be
able to read multiple .exec files and produce combined numbers in the UI,
but it will not produce a resulting "merged" .exec file. For this you will
need to look at the underlying JaCoCo library/tooling and find out if
Sorry but this list is mostly for the jenkins plugin. For detailed
questions about JaCoCo itself, you will need to use other places to
discuss, e.g. StackOverflow or resources listed at
https://www.jacoco.org/contact.html
Regards... Dominik.
On Tue, Sep 20, 2022 at 8:27 AM Mehul Parmar
wrote:
>
> On Tue, 20 Sep, 2022, 1:37 pm Dominik Stadler,
> wrote:
>
>>
>> Sorry but this list is mostly for the jenkins plugin. For detailed
>> questions about JaCoCo itself, you will need to use other places to
>> discuss, e.g. StackOverflow or resources listed at
>>
Hi,
Unfortunately there is currently no functionality which can re-use
exclusions and other configuration from pom.xml/build.gradle so you need to
keep them twice.
As there are many different ways how this could be specified in the various
build-systems, it would be hard to do this in a general f
97 matches
Mail list logo
