I am doing code anaylysis using SonarQube version 4.3 with Sonar Runner 2.4. But I don't see RCI (Rules compliance index) which was there in version 3.7.
Question:
is RCI replaced by Technical Debts ? (as in SONAR-4820)
is it possible to view RCI in SonarQube version 4.3, if so how ?
FYI #goodspeed, we're going to reintroduce this RCI metric by publishing a dedicated plugin. I expect this plugin to be released by the end of July.
After searching for some time, I found out that RCI is deprecated from default widget after SonarQube 4.0. Refer the following for more info:
1) http://jira.codehaus.org/browse/SONAR-4755
2) http://sonarqube.15.x6.nabble.com/Sonarqube-4-2-Rules-Compliance-Metric-missing-tt5023713.html
Related
I just upgraded from SonarQube 6.1 to 6.7.7. For SonarJava, it automatically installed 4.15.0.12310 (it was 4.10.0.10260 before). In the Marketplace, when I hover over the available versions from 5.0-5.13, it says “Incompatible”. When I hover over 5.13.1+, it says “Requires system update”. What does it mean for it to be incompatible if it doesn’t require a system update?
I am seeing this with various other plugins as well, such as SonarPython, which had 1.8 automatically installed. I had to manually install 1.9.1 in order to get this bug fix (which is why I originally upgraded the server): https://community.sonarsource.com/t/python-s1481-code-smell-unused-local-variables-should-be-removed-false-positive-with-string-interpolation/8961
I could manually install newer versions of other plugins as well, but I don’t know if that’s safe.
I also can’t find an official plugin compatibility matrix, since this only shows 7.9+: https://docs.sonarqube.org/latest/instance-administration/plugin-version-matrix/
Incompatible means that the plugin does not work with the version of SonarQube you have installed.
An example of an incompatible plugin would be one where the plugin relied on an API that was removed in your current SonarQube version. You may be able to use that version of the plugin if you downgraded your SonarQube instance to a previous version.
Requires system update means you need to upgrade SonarQube in order to install the plugin.
For what it's worth, the states as described by the API documentation are:
Update status values are:
COMPATIBLE: plugin is compatible with current SonarQube instance.
INCOMPATIBLE: plugin is not compatible with current SonarQube instance.
REQUIRES_SYSTEM_UPGRADE: plugin requires SonarQube to be upgraded before being installed.
DEPS_REQUIRE_SYSTEM_UPGRADE: at least one plugin on which the plugin is dependent requires SonarQube to be upgraded.
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.
I updated core C# plugin to 3.1 from the update centre. Once i restarted the service Sonar Service failed to start.
The Log Message :
org.sonar.updatecenter.common.exception.IncompatiblePluginVersionException: The plugins 'csharpstylecop' and 'csharp' must have exactly the same version as they belong to the same group.
After the updated i still see csharpstylecop plugin is 2.1 and i even i don't find the csharpstylecop 3.1 available in the maven repository.
http://mvnrepository.com/artifact/org.codehaus.sonar-plugins.dotnet.csharp/sonar-csharp-stylecop-plugin
Is that a pre-requsite to install the csharpstylecop 3.1 (which is not available) or the C# plugin will take care (which is not happening).
Any help here is appreciated.
Thanks,
Santhosh.
You cannot use the update center to upgrade from the .NET 2.1 plugins to the 3.x series.
Please refer to the following migration guide: http://docs.codehaus.org/x/EIBMDg
My understanding is that Findbugs 3.0.0 will support analyzing Java 8 bytecode. I see that there is a beta version of it available here:
http://sourceforge.net/projects/findbugs/files/findbugs/3.0.0/
SonarQube is waiting until the final version of Findbugs 3.0.0 is released before upgrading their Java plugin to use it. This means SonarQube is unable to analyze our Java 8 projects.
Is there a target date for Findbugs 3.0.0 release or a known workaround for using the beta version of it with SonarQube?
Well, 3.0.0 RC1 is released today (25.06.2014) and we plan to release 3.0.0 final (if there will be no major regressions reported) in July.
Update: 3.0.0 is released on 06.07.2014, see https://mailman.cs.umd.edu/pipermail/findbugs-discuss/2014-July/004029.html
As per mailing list thread : https://mailman.cs.umd.edu/pipermail/findbugs-discuss/2014-May/003999.html
The release is now mainly depending on early adopters feedback.
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.