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/.NET Core scanner.
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 - 8.x. It supports both the community and the commercial editions.
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
(22)Sign in to write a review
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.
Reviews for server
(22)Sign in to write a review
Reviews for Data Center
(22)Sign in to write a reviewHi, 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.
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 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.
- 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.
- 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.
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
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 2.6.3 • Bamboo Server 5.1.0 - 6.10.3 • Released 2019-10-28
Summary
Bug fixes
Details
Bug fixes:* Bamboo variables in project keys and project names are not substituted when using new branching
* Maven variables like groupId/artifactId in project name are not substituted when using legacy branching
Installation
- Log into your Bamboo instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Sonar for Bamboo via search. The appropriate app version appears in the search results.
- 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.
- Enter your information and click Generate license when redirected to MyAtlassian.
- 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
