I would like to upgrade my current sonar installation from 3.0.1 to 3.1 (or higher). As usual, the system checks the compatibility of the installed plugins with the new release. While normally, this is not much an issue, sonar now wants me to remove seven plugins, I rely on. Steps to perform sonar system upgrade (sorry, I can't post a picture):
Sonar 3.1
Date: Jun 13, 2012
Release Notes: Global dashboards, Findbugs 2.0, rules for unit tests
How to upgrade: Follow those steps to upgrade Sonar from version 3.0.1 to version 3.1 :
the plugin Findbugs which is not compatible with Sonar 3.1.
the plugin Surefire which is not compatible with Sonar 3.1.
the plugin Checkstyle which is not compatible with Sonar 3.1.
the plugin PMD which is not compatible with Sonar 3.1.
the plugin JaCoCo which is not compatible with Sonar 3.1.
the plugin Cobertura which is not compatible with Sonar 3.1.
the plugin Squid for Java which is not compatible with Sonar 3.1.
Stop Sonar
Download and install Sonar 3.1 after having carefully read the upgrade guide.
Start Sonar
While I can understand that I would have to uninstall Findbugs as sonar 3.1 switches to Findbugs 2.0, I hardly can imagine that all the other plugins are incompatible with the new sonar minor release. Of course, there are no pending plugin updates.
So, is this normal or is there somewhere an error in the system? What can I do about it?
The warnings can be safely ignored when upgrading to 3.5.1: http://sonar.15.x6.nabble.com/Upgrading-Sonar-3-0-1-gt-3-1-requires-to-uninstall-almost-all-plugins-td5014227.html
Related
Although the build was started using java version: 1.8.0_242, vendor: AdoptOpenJDK, I'm getting the warning -tag option is not supported on Java version < 1.4. When building with javadoc:jar, the build fails because of the custom tags.
This is a quite old build using maven-javadoc-plugin:2.10.4. I cannot just ramp it up to 3+, and 2.10.4 seems to be newest version of 2.10.
Any ideas?
I'm using STS 4.6 and getting below error while using Gradle 6.8.3. I was able to build project using Gradle 4.10 but for JDK 11 I had to upgrade Gradle version. Please assist how to resolve this
Support for clients using a tooling API version older than 3.0 was removed in Gradle 5.0. You are currently using tooling API version 2.2.1. You should upgrade your tooling API client to version 3.0 or later.
I solved this by uninstalling 'Gradle IDE' plugin provided by Pivotal and installing 'Eclipse Buildship plugin for Gradle' - Refer this
I am trying to integrate sonarqube gradle plugin with jdk7 but build is failing due to version mismatch.
Gralde version 4.3
JDK 1.7
Sonarqube-gradle plugin ??
2.0.1 was the last version to support Java 7
https://github.com/SonarSource/sonar-scanner-gradle/releases/tag/2.0.1
https://github.com/SonarSource/sonar-scanner-gradle/blob/2.0.1/build.gradle#L24..L25
We recently installed SCMActivity plugin in our 3.6.1 installation and it worked without a hitch. Now that we are prepping to move to 4.4, installing the same plugin (version 1.8) does not yield same results - svn blame is not working. I am not sure why.
Our setup is all Centos, SVN 1.8, Sonar 4.4, SCMActivity plugin 1.8.
Since SonarQube 4.5, you need to turn on SCM decoration on the Component Viewer to be able to see SCM information. See the documentation on the SCM Tab.
I have Bamboo version 5.2 configured on my local system.
I want to install a sonarqube plugin in my bamboo instance. I found a plugin for version 5.1, but was unable to find a plugin for version 5.2.
From where do I get the appropriate plugin and how to configure the sonar runner task with it?
it is not supported for your version of Bamboo. Its a open source plugin so you can pick it up, work on it and make it compatible with your Bamboo verison