1,947
Customers have installed this app in at least 1,947 active instances.
    by Mibex Software GmbHTop Vendor
    Mibex Software GmbH is a Top Vendor. Top Vendors have high standards for app quality, reliability, and support.

    Learn more

    for Bamboo Server 5.1 - 6.6.3
    Supported
    Mibex Software GmbH supports this app.

    Get support

    Bamboo tasks to analyze Maven, Gradle, MSBuild & SonarQube Scanner projects - supports auto-branching for Sonar-based code reviews

    Bamboo tasks to analyze Maven, Gradle, MSBuild & SonarQube Scanner projects - supports auto-branching for Sonar-based code reviews

    Bamboo tasks to analyze Maven, Gradle, MSBuild & SonarQube Scanner projects - supports auto-branching for Sonar-based code reviews

    Bamboo tasks for Maven, Gradle, Scanner & MSBuild

    Auto-branching and incremental Sonar analysis

    Configurable server settings and build breaker

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

    Supports code reviews with pull requests by automatically setting Sonar's branch parameters. Also provides incremental scans to reduce build time by only analyzing new and changed files of a pull request.

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

    More details

    The app is compatible with SonarQube 4.5 - 7.x and also supports the new branch plug-in.

    If you also use Bitbucket Server, you might as well be interested in our "Sonar for Bitbucket Server" app 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.

    Reviews for cloud

    (20)
    Sign in to write a review
    by Tibor Marchyn on 2017-03-21
    plugin is great and Mibex support too. we've got problem with Sonar 6.3 compatibility and they fixed it same day.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Clint Wadley on 2017-02-13
    Excellent plugin. I found a defect in the MSBuild integration tasks and created a Jira issue for it. Within 12 hours, Michael from Mibex had fixed it and sent me a beta version. Needless to say, awesome support. SonarQube is now running on my .Net project without a hitch. Thank you!
    Was this review helpful?YesNo
    by Richard Cross on 2016-10-14
    UPDATE: There have been several updates since my original review, some of which were in direct response to my feedback. The good news is that the issues I cited below are now all fixed, and the Runner task can now directly replace the equivalent task from the old Marvelution plugin (which means I can get rid of that old plugin finally!). Accordingly, I have bumped the score up to 4 stars, as I cannot now find any fault with this plugin. 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?
    3 out of 3 found this review helpful
    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 Fabiano Koseki 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

    Reviews for server

    (20)
    Sign in to write a review
    by Michael Benz on 2018-09-11
    Very nice add-on. Waiting to check out the incremental code changes feature. Now switched to a paid model with version 2.0 with moderate pricing and quality gate checks through webhooks.
    Was this review helpful?YesNo
    by Oliver Strässer on 2018-08-13
    Thank you for that app, it helped us to improve our dev cycle lot!
    Was this review helpful?YesNo
    by Sébastien Vermeille on 2018-05-09
    Really a great plugin. We use it internally and it helps a lot. Big thanks to the authors: I had a feature request to support Java 10 they fixed it in less than 3 hours after my request a new release were present
    Was this review helpful?YesNo
    by Ladislav Kis on 2018-05-04
    Without the incremental analysis that this plugin allows, it would not be possible to use Sonar on our multi-million-line code base. The full analysis takes about an hour, but with a typical pull request only containing a handful of files, the incremental analysis takes just seconds. What is perhaps even better than the plugin is the support the author provides. I have had several interactions (whether due to our peculiar process, operating system limitations, or changes in the plugin behavior) and each time they listen, respond promptly, work with you to solve the problem, and if necessary, quickly make enhancements to the plugin. Every time I had a reasonable suggestion, they would make it happen.
    Was this review helpful?YesNo
    by Tibor Marchyn on 2017-03-21
    plugin is great and Mibex support too. we've got problem with Sonar 6.3 compatibility and they fixed it same day.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo

    Reviews for Data Center

    (20)
    Sign in to write a review
    by Tibor Marchyn on 2017-03-21
    plugin is great and Mibex support too. we've got problem with Sonar 6.3 compatibility and they fixed it same day.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Clint Wadley on 2017-02-13
    Excellent plugin. I found a defect in the MSBuild integration tasks and created a Jira issue for it. Within 12 hours, Michael from Mibex had fixed it and sent me a beta version. Needless to say, awesome support. SonarQube is now running on my .Net project without a hitch. Thank you!
    Was this review helpful?YesNo
    by Richard Cross on 2016-10-14
    UPDATE: There have been several updates since my original review, some of which were in direct response to my feedback. The good news is that the issues I cited below are now all fixed, and the Runner task can now directly replace the equivalent task from the old Marvelution plugin (which means I can get rid of that old plugin finally!). Accordingly, I have bumped the score up to 4 stars, as I cannot now find any fault with this plugin. 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?
    3 out of 3 found this review helpful
    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 Fabiano Koseki 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

    Cloud Pricing

    Server Pricing

    Data Center Pricing

      Local agents only
    10 jobs
    $10
    1 remote agent
    Unlimited jobs
    $88
    5 remote agents
    Unlimited jobs
    $242
    10 remote agents
    Unlimited jobs
    $440
    25 remote agents
    Unlimited jobs
    $880
    100 & upAdditional pricing details

    Pricing FAQ

    How does server app pricing work?

    Server products and apps are hosted on your servers. This app is sold as a perpetual license, and the purchase price includes 12 months of maintenance (support and version updates).

    You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your Atlassian product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my server pricing?

    Apps are billed based on the number of users in your Atlassian product. The app tier should match the licensed user tier of the Atlassian product. For example, if you have a Confluence license for 500 users, you should purchase the 500-user tier for apps. Even if fewer users want to use the app than your Atlassian product license, the two licenses should match exactly.

    Can I install this app in a Data Center product?

    This app does not have a a Data Center approved version. Only apps meeting a set of performance requirements for large, clustered environments are approved for Data Center.

    However, while server apps are built for single-server deployments, many customers successfully install them in Data Center products. If you're using a Data Center product, Atlassian recommends you contact the vendor to determine compatibility at scale.

    Learn more about Data Center approved apps

    What type of license do I need if I'm using this app in a Data Center product?

    Because this app does not have a Data Center approved version, you should purchase a Server license if you decide to install this app in a Data Center product.

    Learn more about Data Center licensing

    Do you offer academic, community, or open-source licenses for server apps?

    For server apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.

    Community and open-source licenses are available for server apps. Learn more about community and open source licenses.

    Can I extend my free trial?

    For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.

    How can I buy apps for my legacy Jira Server or Confluence Server license?

    If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:

    • Purchase the app at the non-legacy Unlimited (10000+ users) tier.
    • Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.

    Learn more

    Mibex Software GmbH is a  Top Vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.

    Vendor support resources

    Documentation

    Find out how this app works.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.

    Versions

    Version 2.0.3 Bamboo Server 5.1 - 6.6.3 Released 2018-08-28

    Summary

    Bug fixes

    Details

    Bug fixes:

    * NPE when creating Sonar task under certain conditions

    Installation

    1. Log into your Bamboo instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. 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. The appropriate app version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Sonar for Bamboo. You're prompted to log into MyAtlassian. Sonar for Bamboo begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Bamboo instance.

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

    Similar apps