Thanks for the reply...
Seems to be that the directory I had for "Use custom workspace" didn't have
the project name in there, but rather just "D:\workspaces". This worked
fine for my source control system, though the mapping was doubled.
So now, I use "D:\workspaces\job01" and Jacoco looks on
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
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 ea
