I'm working in the sonarqube 3.7.4. I analysed my java project and it clearly showing me the number of issues with the count. But while clicking the issues it results in "No matching issues found".
Please provide me the suggestion to fix the issues
You should upgrade to the latest LTS version of SonarQube : 4.5.6
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 upgraded my SonarQube from 5.4 to 5.6 LTS then to 6.3.1 then 6.4
On the version 6.4, when I click on the dashboard, I only see the projects' names but no results are displayed.
In addition I have a rotating frame of the project as if it loads.
Plus, When I click on the project, I have 0 bugs, 0 vulnerabilities .... which is wrong because when I click on issues, I can see that the project do have issues and I can display them.
It's the case with the projects analyzed with the previous versions only. I tried analyzing a project with 6.4 and the results related to Reliability, Security, Maintainability... are there.
Is there a way to fix this, ie to display on the dashboard of SonarQube 6.4 the results of projects analyzed by older versions?
Thanks in advance.
The fix is planned for SonarQube 6.5 (see the ticket).
This sounds like a corrupted ElasticSearch index. Try the following:
stop the server
delete _$SONARQUBE_HOME/data/es_
restart the server*
*The time for you server to come back up will vary based on how large the instance is
I see, thank you for your help. Just to let you know, even when I click on the project , I cannot see the results, they are only available when I click on Issues
Just found a bug regarding "Do not include complexity of nested functions into nesting one complexity".
https://jira.sonarsource.com/browse/SONARJS-729
It say's its fixed with version 2.15 in sonarsource. But i'm unable to find in what version of SonarQube, the same is fixed. Right now, we use SonarQube version of 4.5.6, but the issue still persist in that version.
SonarJS 2.15 is not compatible with SonarQube 4.5.6: since version 2.14, SonarJS requires SonarQube 5.6 or later.
You need to first upgrade to SonarQube 5.6 or later, and then upgrade SonarJS.
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
Sonarqube 4.1.2 with the latest php-plugin is not detecting any violations.
When I run the analisis with Sonar 4.2 it shows me the errors how I expected them.
Is there a bug related to the php-plugin? Can anyone confirm this behaviour?
Thanks in advance
When using SonarQube 4.1.2, could you double check the content of the PHP quality profile that you're using ? Indeed in latest versions of the PHP plugin, all rules have been rewritten so if you have also upgraded the PHP plugin perhaps you're simply doing an analysis with an empty quality profile.