Sonar for Bamboo

plugin is great and Mibex support too. we've got problem with Sonar 6.3 compatibility and they fixed it same day.

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!

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?

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

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...