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
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 making a Java program which will be deployed to the Google App Engine and I'm using the Cloud SDK maven plugin version 2.4.0 to deploy to the GAE. However when I run mvn package appengine:deploy the cloud SDK will say its current version is 321.0.0 and needs to update to 327.0.0. The update will then fail with the error:
ERROR: (gcloud.components.update) Access is denied: [C:\Users\jamie\AppData\Local\Google\ct4j-cloud-sdk\LATEST\google-cloud-sdk.staging\platform\kuberun_licenses\LICENSES.txt]
However when I just run gcloud components update I get the result of All components are up to date.
Anyone know why this may be happening or how to fix it?
EDIT: As a work-around I found you can force the maven plugin to use a specific version of the sdk by using <cloudSdkVersion>321.0.0</cloudSdkVersion>. I'm still very curious to know why this occurred though
Manged to fix this by deleted the whole C:\Users\jamie\AppData\Local\Google\ct4j-cloud-sdk folder as this forces the plugin to redownload a fresh SDK.
The error occurs as the plugin uses its onw auto managed SDK rather than the one which is user managed.
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.
My organization is using sonarqube:7.1 with sonar-bitbucket-plugin-1.2.3 (https://github.com/mibexsoftware/sonar-bitbucket-plugin) and everything is working fine. We are planning to upgrade to sonarqube:7.5 and while I was testing all the existing plugins, sonar-bitbucket-plugin is causing the issue(It's not supported in the newer version of Sonarqube). I want to upgrade to 7.5+ version of Sonarqube and want sonar-bitbucket-plugin as well. Could someone please help me out?
ERROR web[][o.s.s.p.Platform] Background initialization failed. Stopping SonarQube
java.lang.IllegalStateException: Fail to load plugin Bitbucket for Sonar [sonarbitbucket]
This community plugin was relying on the deprecated preview/issues analysis mode to analyze pull requests, that was finally removed.
Since SonarQube 6.7 the support of branches (and then pull requests) analysis has been properly integrated on the server side. Decorating PR was added progressively for various ALM, and for Bitbucket Server it is supported since 7.7.
Note that all branch/PR features are only available in commercial editions (or for free on SonarCloud for open source projects).
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.