In my workspace I have a separate folder for sources and one for builds. The build is performed from the build folder and due to this the issues reported by the compiler are reported for file something like

..\src\mysrc.c:625:16: warning: some text

I capture all build log into a file and provide this log file to the scanForIssues() pipeline step using something like:

dir('builddir') { scanForIssues(tool: clang(pattern: 'build.log', reportEncoding: 'UTF_16LE')) }

I tried to run the scanForIssues from the root providing full link to the log file, from the builddir, providing sourceDirectory:pwd() (also adding the path to the Jenkins configuration) with no success. The issues are reported but the files are not found correctly and the issue from the web isn't clickable to show me the exact location in the file's context.

I see something like this in the console log:

[2022-01-07T18:24:43.122Z] [Clang] -> 0 copied, 4 not in workspace, 0 not-found, 0 with I/O error

Do I need to set up my build differently or is this a bug in the tool?

I am using plug-in version 9.0.1 and Jenkins 2.277.3. Master is Linux, build slave is Windows 10.