SonarQube upgrade from 9.7 to 9.8 breaks C++ project analyses

SonarQube Server / Community Build
,
1

Following an upgrade of SonarQube from 9.7 to 9.8, our C++ project analyses all fail.

The Bamboo logs all show this exception being thrown:

org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘org.sonarsource.scanner.api.internal.IsolatedClassloader@57c758ac-org.sonar.scanner.bootstrap.ScannerPluginRepository’: Initialization of bean failed; nested exception is java.lang.IllegalStateException: Fail to parse response of api/plugins/installed

and ultimately:

Caused by: You’re not authorized to run analysis. Please contact the project administrator.

Can anyone suggest why the upgrade has broken the analyses?

I’ve tried to solve the problem with the steps below, so far without success:

  • Have updated sonar-scanner to latest version (sonar-scanner-5.0.1.3006 - was using an earlier version)
  • Have created a dedicated analysis user on the server
  • Have granted the analysis user the privilege to execute analyses
  • Have created a global analysis token for the user.
  • Have supplied the token on the sonar-scanner command-line via -Dsonar.token=

The common sonar configuration file contains settings for the following values:
sonar.sources
sonar.cfamily.cppunit.reportsPath
sonar.inclusions
sonar.cfamily.build-wrapper-output
sonar.cfamily.cache.enabled
sonar.cfamily.gcov.reportsPath
sonar.projectKey
sonar.projectName
sonar.projectVersion
sonar.host.url
sonar.cfamily.threads

Do I need to also set a value for sonar.organization? If so, I’m not sure what value to use since we are using a corporate version of SonarQube and not SonarCloud.

2

Solved. Despite assurances from the server administrators that the account that I was using for authentication was authorised to perform analyses, it turns out that it wasn’t. Having properly added the required permission, the analyses all work correctly now.

I am now setting sonar.login and sonar.password in my configuration file, and I have removed sonar.token from the scanner command-line.

1 Like
3

Hi,

I’m glad you worked through this.

And you should be aware that 9.8 is EOL.

You should upgrade to the current LTS, 9.9.2, or the latest version, 10.2.1 (10.3 imminent) at your earliest convenience.

 
Ann

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.