What could be done in this kind of situation?
As I unsertand, the paths of source codes, are being saved in instrumented jars, so later on they can be used during reports generation(clover), to have the correct links. In this case, when during reports generation it tries to find source codes (java files), it fails, as the sources are located in Machine A but not on machineB.
You can make it other way, i.e. when tests are finished you can copy clover directory (containing clover.db and coverage files) from machine B back to machine A where sources are located.
You can also disable source files access during report generation.
Some more information:
https://answers.atlassian.com/questions/14895/source-path-for-clover-report<br< a="">>https://answers.atlassian.com/questions/240733/are-source-files-mandatory-for-clover-report<br< a="">>
Hi Community! I’m Elaine, Confluence Product Manager. You may have read my earlier post about page tree in space navigation sidebar. I'm excited to share another improvement that helps you organize ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs