927
Customers have installed this add-on in at least 927 active instances.
    by Mibex Software GmbHAtlassian Verified
    Mibex Software GmbH is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for add-on quality, reliability, and support.

    Learn more

    for Bamboo Server 5.1 - 5.13.1
    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Supported
    Mibex Software GmbH supports this add-on.

    Get support

    Get it nowFree add-on

    Bamboo tasks to analyze projects with Sonar for Maven, Gradle & SonarRunner - supports auto-branching for Sonar-based code reviews

    Bamboo tasks to analyze projects with Sonar for Maven, Gradle & SonarRunner - supports auto-branching for Sonar-based code reviews

    Bamboo tasks for Maven, Gradle & SonarQube Runner

    Auto-branching for Sonar-based code reviews

    Configurable server settings and build breaker

    Provides Bamboo build tasks for analyzing projects with SonarQube. Supports builds with Maven (v2+v3), Gradle and SonarQube Runner.

    Supports code reviews with pull requests based on Sonar by automatically setting Sonar's branch property with the used Bamboo plan branch. Rewrites branch names to be compliant with Sonar's project naming restrictions.

    Multiple Sonar server settings can be stored in the plug-in. Includes a build breaker functionality to fail the build if the configured SonarQube quality gates fail.

    More details

    If you also use Bitbucket Server, you might as well be interested in our "Sonar for Bitbucket Server" plug-in which integrates Sonar's code analysis metrics into Bitbucket Server. This allows you to never leave Bitbucket Server when you are doing code reviews and to make them more effective with the integrated Sonar code metrics and violations showing up in its pull request diffs.

    User reviews

    (10)
    Sign in to write a review »
    by Richard Cross on 2016-09-02
    UPDATE: There has been a new release with a new "Additional parameters" input box, but unfortunately it doesn't work. For a start, it ignores newline characters, so you have to remember to put a blank space at the end of each line. But when you do that, you can still get errors such as the following: 02-Sep-2016 19:21:30 ERROR: Unrecognized option: 02-Sep-2016 19:21:30 INFO: 02-Sep-2016 19:21:30 -Dsonar.projectVersion=256 Which I got when I added the following into the Additional Parameters box: -Dsonar.scm.disabled=true -Dsonar.projectVersion=${bamboo.buildNumber} -Dsonar.analysis.mode=${bamboo.inject.SONAR_ANALYSIS_MODE} Unfortunately this still makes it unusable, and so I have to resort to the very old and unsupported Sonar plugin for the time being. Original Review (for posterity): Well, it's free, so can't complain too much... but the Sonar Runner is a huge leap backwards from the Marvelution Sonar Runner plugin, to the extent that it is practically unusable for anything other than Java/Maven projects. The whole point of the standalone runner task should be that you can easily customise your settings it for projects that **don't** use Java, Maven or Gradle, where many properties can be retrieved from the project configuration files (e.g. pom.xml ). In the Runner Task, there are no fields to specify the project name, project key, project version or the paths to sources or tests. These are fields you might commonly want to override with Bamboo build-time variables (particularly the project version). There *are* fields to specify Java Source/Target versions... why? If you're analysing a Java project, then it's almost certain to be run via Maven or Gradle, so you would be using one of those tasks! These are a complete waste of screen space. You are instead forced to specify every single custom property in the "additional parameters" text box, which is a ghastly wraparound free-text field that is only two lines high by default. This makes it horribly difficult to maintain, or spot any errors amongst the 10+ properties you inevitably need to specify. And, most frustratingly... it doesn't even work with remote Bamboo agents without changing a properties file on the remote agent. Bamboo already has a concept of remote Agent "capabilities" which includes a "Sonar Runner" capability. Any Bamboo agent launched with the environment variable SONAR_RUNNER set, has this capability. The Marvelution Sonar Runner task used this capability to obtain the path to the runner. Why must I make another separate change to get this plugin working?
    Was this review helpful?YesNo

    Mibex Software GmbH

    Hi, thanks for your feedback.

    The fields you have listed can also be specified in your sonar-project.properties field. This is what most users (we as well for our Scala projects) do, so there is no need to pass them in the "additional parameters" box. But we see that it would be valuable to have them in the task configuration as well in case the values of the Sonar properties are dynamic (e.g., when sonar.projectVersion is based on a Bamboo build variable). So we will provide input fields for them in the SonarRunner task for the next release.

    The plug-in has been successfully tested on remote agents by specifying the path to the SonarRunner in the remote agent config file. While you are right that the path to the executable could also be taken from the capabilities of the associated local / remote agent, it is convenient if you can create the capability from the task itself and don't need to go to the executables section of your Bamboo administration page. This is also consistent with the Maven task built-in to Bamboo which also allows one to configure the path to the Maven executable in the task. But you are right that we should make this an optional field and take the executable from the associated capability if specified. We will change this for the next version of the plug-in as well.

    UPDATE June 26, 2016: We released both input fields for SonarQube parameters and optional executable for remote agents with release 1.4.0 of the plug-in.

    by Jorge Marb on 2015-09-30
    Awesome plugin. Our code review became less time consuming with the automation from bamboo + this plugin. We are using in our production workflow just fine. Thanks
    Was this review helpful?YesNo
    by Madhusudhan Matrubai on 2015-08-25
    Pretty cool plugin and I must say their support was the best, the turn around time to fix a bug that we submitted was amazing. Truly Rocking...
    Was this review helpful?YesNo

    Pricing

    Support

    Mibex Software GmbH supports Sonar for Bamboo. You can visit the support site to get help.

    Get support

    Versions

    Version 1.4.2 Bamboo Server 5.1 - 5.13.1 Released 2016-09-12

    Summary

    Bug fixes

    Details

    Bug fixes:

    * Bamboo task descriptions are not always shown due to I18N issues

    * Separating additional properties with new lines does not work

    Installation

    1. Log into your Bamboo instance as an admin.
    2. Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Sonar for Bamboo via search. Results include add-on versions compatible with your Bamboo instance.
    5. Click Install to download and install your add-on.
    6. You're all set! Click Close in the Installed and ready to go dialog.

    To find older Sonar for Bamboo versions compatible with your instance, you can look through our version history page.

    Similar add-ons