Issue with build wrapper - file was found but 0 C/C++/Objective-C files were analyzed

Hi Team,

We’re using licensed sonarqube and we’re integrating sonarqube with buildkite, this docker image used by the plugin is sonarscannerbuildkite/sonarscanner:0.1.1, this docker image is using sonar-scanner version 4.2.

Our current scenario is to get branch/PR wise analysis by integrating with buildkite we’re using this plugin GitHub - wayfair-incubator/sonarscanner-buildkite-plugin: 🐳🔊 Sonarqube SonarScanner plugin for Buildkite.
So the build-wrapper command we’re executing from a linux host machine and this plugin will basically copy the artifacts bw-output and coverage.xml into the docker container and runs the sonar scanner command. We’re getting the below error when trying the same.

By going through the other issues, I found that it could be because of the absolute paths in build-wrapper-dump.json since it is copied into the container it was unable fine the path. So I’m updating the path of that file to match the container path where our source code is present. But still facing the same issue.

Can someone please help me to fix this issue?

java.lang.IllegalStateException: The "build-wrapper-dump.json" file was found but 0 C/C++/Objective-C files were analyzed. Please make sure that:
  * you are using the latest version of the build-wrapper and the CFamily analyzer
  * you are correctly invoking the scanner with correct configuration
  * your compiler is supported
  * you are wrapping your build correctly
  * you are wrapping a full/clean build
  * you are providing the path to the correct build-wrapper output directory
  * you are building and analyzing the same source checkout, absolute paths must be identical in build and analysis steps
        at com.sonar.cpp.plugin.CFamilySensor.process(
        at com.sonar.cpp.plugin.CFamilySensor.execute(
        at org.sonar.scanner.sensor.AbstractSensorWrapper.analyse(
        at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute(
        at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute(
        at org.sonar.scanner.scan.ModuleScanContainer.doAfterStart(
        at org.sonar.core.platform.ComponentContainer.startComponents(
        at org.sonar.core.platform.ComponentContainer.execute(
        at org.sonar.scanner.scan.ProjectScanContainer.scan(
        at org.sonar.scanner.scan.ProjectScanContainer.scanRecursively(
        at org.sonar.scanner.scan.ProjectScanContainer.doAfterStart(
        at org.sonar.core.platform.ComponentContainer.startComponents(
        at org.sonar.core.platform.ComponentContainer.execute(
        at org.sonar.scanner.bootstrap.GlobalContainer.doAfterStart(
        at org.sonar.core.platform.ComponentContainer.startComponents(
        at org.sonar.core.platform.ComponentContainer.execute(
        at org.sonar.batch.bootstrapper.Batch.doExecute(
        at org.sonar.batch.bootstrapper.Batch.execute(
        at org.sonarsource.scanner.api.internal.batch.BatchIsolatedLauncher.execute(
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.base/java.lang.reflect.Method.invoke(
        at org.sonarsource.scanner.api.internal.IsolatedLauncherProxy.invoke(
        at com.sun.proxy.$Proxy0.execute(Unknown Source)
        at org.sonarsource.scanner.api.EmbeddedScanner.doExecute(
        at org.sonarsource.scanner.api.EmbeddedScanner.execute(
        at org.sonarsource.scanner.cli.Main.execute(
        at org.sonarsource.scanner.cli.Main.execute(
        at org.sonarsource.scanner.cli.Main.main(

Hey there.

What version of SonarQube are you using (it should be in the footer of your SonarQube instance)?

Hey Colin,

Thanks for the response, we’re using Developer Edition Version 9.1


Your version is past EOL. You should upgrade to either the latest version or the current LTS at your earliest convenience. Your upgrade path is:

9.1 → 9.9.1 → 10.1 (last step optional)

You may find these resources helpful:

If you have questions about upgrading, feel free to open a new thread for that here.

If your error persists after upgrade, please come back to us.

Thanks for the suggestion Colin!

But do you think upgrading the sonarqube will fix this issue?

I’m not sure – but at least we’ll be troubleshooting a supported version of SonarQube, instead of an EOL version.