That is quite surprising. I have many different Jacoco based jobs running on master and on slaves and on Windows and Linux and have never seen it "wandering" outside its own directory path to find coverage data.
Could there be a symbolic link (or the Windows equivalent of it) inside the workspace directory which is causing the matcher to look "one directory above" the workspace? Could there be a directory definition somewhere in the system configuration (like the path to the C:\workspaces directory) which would benefit from a trailing slash to stop the matcher from somehow looking outside the workspace? Mark Waite On Wed, Jul 30, 2014 at 4:40 PM, Mark Wilhelm <artisancreekbrew...@gmail.com > wrote: > Hello, > > I'm running a Jenkins server with multiple jobs. Part of one of the jobs > is to run Jacoco for code coverage metrics. I am using the latest Jacoco > plugin. What is happening is that the Jacoco run is going into every job > and searching for Jacoco artifacts (classes, exec,etc...) and with each new > job, the build is taking longer and longer. > > How do I limit Jacoco from traversing all the paths? Is it with > exclusions? If so, how do I enter the paths to exclude? > > Sorry if this is in the wrong group, but thought this could be Jenkins > issue (default workspaces?) > > Thank you. > > For example: > > C:\Program Files (x86)\Jenkins\jobs\job01 > \job02 > \job03 <- has Jacoco > plugin task > \job04 > \jobn... > > C:\workspaces\job01\src > \job02\src > \job03\src > \job04\src > \jobn... > > *Jacoco coverage example:* > [JaCoCo plugin] Collecting JaCoCo coverage data... > [JaCoCo plugin] **/**.exec;**/classes;**/src/main/java; locations are > configured > [JaCoCo plugin] Number of found exec files: 4+n > [JaCoCo plugin] Saving matched execfiles: > C:\workspaces\job01\src\jacoco-unit.exec > C:\workspaces\job02\src\jacoco-unit.exec > C:\workspaces\job03\src\jacoco-unit.exec > C:\workspaces\job04\src\jacoco-unit.exec > C:\workspaces\jobn\src\jacoco-unit.exec > [JaCoCo plugin] Saving matched class directories: > C:\workspaces\job01\src\classes > C:\workspaces\job02\src\classes > C:\workspaces\job03\src\classes > C:\workspaces\job04\src\classes > C:\workspaces\jobn\src\classes > [JaCoCo plugin] Saving matched source directories: > C:\workspaces\job01\src\java > C:\workspaces\job02\src\java > C:\workspaces\job03\src\java > C:\workspaces\job04\src\java > C:\workspaces\jobn\src\java > [JaCoCo plugin] Loading inclusions files.. > [JaCoCo plugin] inclusions: [] > [JaCoCo plugin] exclusions: [**/*Test*.class] > [JaCoCo plugin] Thresholds: JacocoHealthReportThresholds [minClass=0, > maxClass=0, minMethod=0, maxMethod=0, minLine=0, maxLine=0, minBranch=0, > maxBranch=0, minInstruction=0, maxInstruction=0, minComplexity=0, > maxComplexity=0] > [JaCoCo plugin] Publishing the results.. > [JaCoCo plugin] Loading packages.. > [JaCoCo plugin] Done. > Sending e-mails to: m...@example.com > Finished: SUCCESS > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Thanks! Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
