MSBuild.SonarQube.Runner throwing error while trying to execute GIT SCM

[ssuk...@gmail.com]

Hi,

I am trying to analyse .NET project using MSBuild.SonarQube.Runner. The project is stored in GIT source control. When SCM adapter is enabled, the analysis fails at step when sonar is trying to get SCM blame information. I am using GIT SCM provider plugin version 1.1. Please advise.

4:24:34 PM  16:24:34.993 INFO  - Sensor SCM Sensor
4:24:34 PM  16:24:34.993 INFO  - SCM provider for this project is: git
4:24:34 PM  16:24:34.999 INFO  - 3 files to be analyzed
4:24:35 PM  INFO: ------------------------------------------------------------------------
4:24:35 PM  INFO: EXECUTION FAILURE
4:24:35 PM  INFO: ------------------------------------------------------------------------
4:24:35 PM  Total time: 32.047s
4:24:35 PM  Final Memory: 16M/64M
4:24:35 PM  INFO: ------------------------------------------------------------------------
4:24:35 PM  ERROR: Error during Sonar runner execution
4:24:35 PM  ERROR: Unable to execute Sonar
4:24:35 PM  ERROR: Caused by: java.lang.LinkageError: org.eclipse.jgit.diff.DiffConfig
4:24:35 PM  ERROR: Caused by: org.eclipse.jgit.diff.DiffConfig

Thanks,

Sukhveer

[Julien HENRY]

Hi Sukhveer,

This error is very strange. What is the version of Java installed on your box (java -version) ? It would also be interesting to have the full stack trace.

++

Julien

[ssuk...@gmail.com]

Hi Julien,

Thanks for the response. The java version is 1.7.0 (Windows server 2008). How can I enable full stack trace? I am running these commands though Jenkins:

1. MSBuild.SonarQube.Runner.exe begin /k:"key-name" /n:"project-name" /v:"%BUILD_NUMBER%"

2. Execute msbuild on project solution

3. MSBuild.SonarQube.Runner.exe end

I chose this way because the Sonar execution though plugin didn't work earlier because of this error:

SonarQube runner executable was not found for sonar-runner

The sonar-runner was set to proper path where executable is located, so not sure why I got this error.

Thanks,

Sukhveer

[ssuk...@gmail.com]

Julien,

I pointed java_home to different JRE (1.7.0.75) and error went away! Thanks for pointing java.

Regards,

Sukhveer

[Julien HENRY]

Cool, thanks for the feedback!