Hi, If it may be still of use for someone: I had the same error case and at the end the problem lied in the fact that in the CPPTest report the files had an absolute path (ie. tested="/dir1/dir2/dir3/file" when the file was physically in $WORKSPACE/dir1/dir2/dir3/file) and this lead to troubles in the file search routine of the Jenkins slave. Removing the leading slash (for example via sed) would solve the problem and all the files would be directly reachable from Jenkins as expected.
Regards, F. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/384d68ed-f09b-4abf-837d-4dad594cfa8f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
