I upgraded sonarqube to 5.2. I replaced the old instance with a new instance, so the old configuration was deleted and replaced.
I have several custom fxcop rules.
When running the analysis, I am getting the following error.
ERROR: Error during Sonar runner execution
ERROR: Unable to execute Sonar
ERROR: Caused by: Unable to find the rule key corresponding to the rule config key "HSI1009" in repository "fxcop".
This is caused by empty entries in the sonar created file fxcop-sonarqube.ruleset file.
Does anyone know if this is a bug or some error on my end? I did not have these sorts of issues before the 5.2 upgrade, but unable to go back due to reliance on some plugins using 5.2.
I was only able to fix this by downgrading back to SonarQube 5.1.2. Even though I am using the same C# plugin (5.0) and the same runner version (2.5), upgrading to SonarQube 5.2 and up broke custom fxcop rules.
This problem has been fixed with the SonarQube Scanner for MSBuild v1.0.2+ : https://jira.sonarsource.com/browse/SONARMSBRU-151
Also be sure to run the SQ Scanner for MSBuild in a .NET 4.5.2 context.
Related
I’m facing issue in SonarQube, Projects are not getting loaded post upgrade from version 7.9.2 to 8.9.0. Though Sonarqube analysis is not failing as it shows the number of projects but it doesn’t list down.
After this upgrade the customized plugins for mulesoft and IIB are also not getting loaded. Which we used to inject at path, /Conf/extensions/Plugins, during deployment.
Screenshots:
Screenshot of how exactly it looks like
I'm using SonarQube 6.2 and I set the Leak Period to "previous_version". However, during analysis, SonarQube detects error in files that were not detected in the previous analysis and in which there was no commit made in the current analysis.
Is this a bug or an issue with my configuration?
By updating the Java analyzer, new issues are detected on files that were not modified. We're aware of the problem. It's fixed in SonarQube 6.3 with SONAR-8736
Before I upgraded Sonar 5.0 I used the internal org.codehaus.sonar:sonar-maven-plugin:4.3.2. After the upgrade I used the same plugin in version 5.0 but got the error
Failed to execute goal org.codehaus.sonar:sonar-maven-plugin:5.0:sonar (default-cli) on project at.biac.offer.pom: Please update sonar-maven-plugin to at least version 2.3
Then I switched to org.codehaus.mojo:sonar-maven-plugin:2.5 but now I get the following error
org.sonar.jpa.session.DatabaseException: Database schema must be updated [version/required=721/170]. Please browse to your sonar homepage.
Is there any way to fix this problem without loosing my analysis data so far?
Database upgrade is a normal step when doing an upgrade of the SonarQube server. You should not lose any data.
After upgrading to Sonar to 4.2, I have errors on some projects with these logs :
The resource '...' is duplicated in database
I had to manually remove the duplicate lines in the database as i didn't know what is the snapshot that provokes this behavior, or if it's du to Database upgrade.
Hope to understand what has going on as i should upgrade other Sonar servers to version 4.2
The issue you're facing relates to a bug that we're currently investigating. Follow the following thread of discussion to get some news about the fix : http://sonar.markmail.org/thread/rgpwforpxm6elnc7
I have upgraded my sonar version from sonar-3.2 to sonar-3.5.1 and upgraded sonar-runner from sonar-runner-1.1 to sonar-runner-2.2.2, now when i am deploying project on newly installed sonar 3.5.1 it run successfully and showing ANALYSIS SUCCESSFUL, it also show project name on sonar server when i use localhost:9000 on browser but code is not showing there, no violations are coming etc.
i am using sonar in two ways and both results the same. Two ways are:
1. using sonar standalone through sonar runner from cmd.
2. integrating sonar with Jenkins(1.515) and using maven(3.0.4)
when i do sonar analysis on sonar 3.2 everything is working fine in both of the above cases but problem comes only when i use sonar 3.5.1.
Can anybody help me out on this issue??
Please suggest what would be the possible way to overcome this issue..
your revert will be appreciable.. Thanks in advance!!
Please refer below for logs
and sonar dashboard
So I do confirm that the Sonar Java plugins have been deleted from the extensions/plugins directory and that's why you don't get any measures/violations when analysing a java project. Here is the link to download version 1.2 of the Sonar Java plugin ecosystem : http://docs.codehaus.org/download/attachments/230396085/JavaEcosystem-1.2.zip. You just have to decompress this archive, place all jar(s) in the extensions/plugins directory and relaunch the Sonar server.