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
Related
I've saw in https://sonarcloud.io/project/activity?id=ch.ge.ve%3Aadmin-offline%3Adevelopment that the activity page view shows some charts on how the project evolved on time.
I'm using Sonarqube docker 6.4 version and there is no charts on that page and I don't know if it's a version problem or what else.
I'm analyzing php projects. Maybe the problem is here?
Does any one knows what's happening?
An screenshot of the example in https://sonarcloud.io/project/activity?id=ch.ge.ve%3Aadmin-offline%3Adevelopment
Thank you.
Those charts are introduced in 6.5. SonarCloud is running the current 6.5 RC, which is why you see graphs there. Since you're running 6.4, it is normal and expected that you don't have graphs.
I'm using the latest version of SonarQube. Is it possible to display the front "Projects" dashboard with just covering the leaks period?
This is not possible in SonarQube 6.3, but it will be implemented in SonarQube 6.4 for sure.
You can watch the ticket SONAR-8912 that we'll soon start working on.
My project is analysed by SonarQube for every VCS check-in and I have observed some strange behavior:
The dependency cycle-count changes to extremes every now and then.
When viewing the details (e.g. clicking the link) the old (smaller number) value is displayed. What could be the cause of this?
This feature has been dropped from SonarQube platform in version 5.2 thus even if there might be some flaws on this on sonar java analyzer side there is not point to make an effort to fix them as this will be dropped when it will move to LTS version 5.x
See this ticket for detailed explanation : https://jira.sonarsource.com/browse/SONAR-6553
I'm trying to use SonarQube Eclipse plugin (version 3.4) along with SonarQube version 3.7.4, Eclipse Kepler and a mulit-modules maven project and I'm facing the following issue.
After having run a local analysis (in preview mode as incremental mode is not possible with 3.7.4) , all issues appear twice. I checked their properties and see that I have for each issue A the following :
A1. issue that is created before the local analysis (probably taken from server)
A2. issue that is added after the local analysis
Both are marked in the view as being "old issues" (new issue = false.)
If I add new issues, they are correctly added to the list. However if I fix an old issue, A2 is removed but A1 still remains in the view (which is rather annoying).
Am I doing something wrong ? Is there a way in order to have only issues displayed once ?
Note : the Eclipse project is correctly associated to the SonarQube component (I'm working with multi-modules projects)
Thank you in advance,
This is a know bug that is referenced here: SONARIDE-426
Feel free to watch it and vote for it.
Sonar is an open platform to manage code quality. I have the admin access to perform the updates. Recently I tried performing a version update from 3.7.3 to 4.1.1.Unfortunately 4.1.1 is only compatible with IE9 or above. Hence I back out the changes as in our organization IE8 is the internet browser. Now 3.7.3 is not working as it is showing as database is pointing to a latest version.MySQL is used to hold the sonar data. I am completely stuck with the issue. Sonar is a very important tool for us as this can only take a code coverage metrics for the source code.
May I request you to look in to this issue and provide some help. I cannot move forward without your help.
Anticipating your help and support.
The only way to get back to a normal state is to start over from a 3.7.3 database backup.