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
hello,
I'm setting up a job to inspect our code using cpptest plugin, and seems
depending on static code analysis plugin.
the parasoft's cpptest in the build environment works well, and Cpptest
warnings are well collected too. but when we look into the warning details
reported by plugins, which
