Question regarding running sonar scanner after building with build wrapper

[Dudi_Avraham]

my sonar scanner fails and i think it is related to the build paths vs the scanner path

1.i am running the compilation in a container from /tmp/pelican with --out-dir /tmp/pelican/out_sonar
2. then i run the same docker image for the scanner from /tmp/pelican
where i have the property below in the properties file
sonar.cfamily.build-wrapper-output=/tmp/pelican/out_sonar

but.
the build files of the compilation (not of the wrapper) are in /tmp/pelican/out/blackwell

my question is:
does the sonar.cfamily.build-wrapper-output propery need to direct to the compiled files also ? or they are not relevant ?

[Colin]

@Dudi_Avraham

does the sonar.cfamily.build-wrapper-output propery need to direct to the compiled files also ? or they are not relevant ?

They aren’t relevant!

The sonar-scanner should execute from the parent directory of the source code you want to scan, and sonar.cfamily.build-wrapper-output should point to the output directory you specified for the build wrapper (out_sonar)