Hi there! here is my sonar configs
During analysis returns
WARN: Could not resolve 86 file paths on my lcov.info, i used verbose to see the logs and all my ts files are unresolved… after searching a bit I found some cases where they set the SF of the lcov with the absolute path, but it also didn’t work. Any idea?
The paths should either be absolute from server root, or match what SonarQube sees in the analysis directory.
How did the paths in the report compare to paths that start from where analysis is kicked off?
Hi @ganncamp ,
Thank you for your answer
In both cases I am using the absolute path
Was the LCOV report produced on the same build agent where you’re analyzing? I.e. are the file paths correct for the machine where analysis is running?
Yes they are, because they are not hardcoded for an absolute path, but dynamically elaborated on the machine where the analysis is performed, we do this via path.resolve
So you’re saying you post-process your LCov report to make sure the paths match the absolute paths present on the analysis agent?
Anything unusual about these paths? Links or dots (e.g.