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
Related
I want to install Maven on Jenkins. Now I can only choose 3.3.9 or older and not 3.5.0 (version which I need).
I'm on an older version of Jenkins (1.651.3). How can I sync this?
How can I get newer maven versions in my installer in Jenkins?
I want to use perforce as SonarQube 5.3 scm provider, but it failed with this error message:
ERROR: SCM provider was set to "perforce" but no SCM provider found for this key.
Supported SCM providers are svn,git
I want to install perforce plugin in SonarQube update center, but it said:
Error while downloading plugin 'scmperforce' with version '1.4'.
No compatible plugin found.
And I can't find any available scm perforce plugins on the SonarQube website.
How to use perforce with SonarQube 5.3?
The current version of SonarQube is 6.4 and the current LTS is 5.6.6. Plugin versions only compatible with versions lower than those have been purged from the Update Center.
There is, however, a version of the Perforce plugin that's compatible with 5.6.6.
In previous version of Jenkins it was possible to install maven with auto installer. but from Jenkins 2.0 it seems to that feature is not provided. where is the place to auto install maven in Jenkins 2.0
You can see maven auto installation inside Manage Jenkins | Global Tool Configuration
Also you may need to install the maven plugin separately for building Maven project
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 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