Sonar 2.8 in screenshots

The Sonar team is proud to announce the release of Sonar 2.8. As usual, this new release includes improvements, bug-fixes and also new features that we believe are worth stopping your daily work for a couple of minutes to check out.

The main functionality is the support of manual code reviews. Coming back to the wikipedia definition of code review…

Code review is systematic examination of computer source code. It is intended to find and fix mistakes overlooked in the initial development phase, improving both the overall quality of software and the developers’ skills. Reviews are done in various forms such as pair programming, informal walkthroughs, and formal inspections.

… there are clearly two sides : automated and manual. Until version 2.8, Sonar only supported automated code reviews.

Manual code review

A human dimension has been added to automatic inspection with three new features :

  • Discussions about violations
  • Assignment of violations
  • Flag violations as false-positives. They will be ignored during next analysis.

review1

review2

review3

review4

review5

Project violations

Sometimes violations do not relate to a specific package or file but to the entire project. It’s for example the case with the Clirr plugin when a class should not have been removed. Such violations are now fully integrated to the violations drilldown page :

Project violations

Compare Quality profiles

A new service provides the capability to compare two Quality Profiles. It highlights differences between rules configurations : rules only activated in one profile and rules activated with different settings.

Compare profiles

Thanks to Julien Henry (Serli) for this great contribution.

So, what is going to keep us busy next ? We believe that manual code reviews add a new dimension to Sonar and this dimension must be integrated as much and simply as possible to the development process and especially to sonar-eclipse.

This is time to now let you give a try to the new version. The release notes of Sonar 2.8 are available in the download page. Reading the installation or upgrade guides is much recommended.

  • Regarding manual code reviews: will you allow general reviews of code that isn’t associated with a violation? We currently use Code Collaborator, which is decent, but I’m wondering if you’re heading in the same direction.

    Also, is there a way to extract metrics from the reviews?

  • Hi Rich, indeed Sonar 2.8 is just a first step and the ultimate goal is to allow users to create review on any piece of code with ou without violation. Moreover there is a web service API to request reviews.

  • Hi,

    I tried to install Sonar 2.8 but i had the following error. How can i handle this error? Could you help me, please..

    Application initialization failed: undefined method `instance_config’ for #
    from file:/C:/sonar-2.7/war/sonar-server/WEB-INF/lib/jruby-rack-1.0.0.1.jar!/jruby/rack/booter.rb:19:in `boot!’
    from file:/C:/sonar-2.7/war/sonar-server/WEB-INF/lib/jruby-rack-1.0.0.1.jar!/jruby/rack/boot/rack.rb:10
    from file:/C:/sonar-2.7/war/sonar-server/WEB-INF/lib/jruby-rack-1.0.0.1.jar!/jruby/rack/boot/rack.rb:1:in `load’
    from :1

  • Hi,

    I tried to install Sonar 2.7, not 2.8 :) Sorry :)

  • Application initialization failed: undefined method `instance_config’ for # Java::OrgJruby::Ruby:0x15e3dc4
    from file:/C:/sonar-2.7/war/sonar-server/WEB-INF/lib/jruby-rack-1.0.0.1.jar!/jruby/rack/booter.rb:19:in `boot!’
    from file:/C:/sonar-2.7/war/sonar-server/WEB-INF/lib/jruby-rack-1.0.0.1.jar!/jruby/rack/boot/rack.rb:10
    from file:/C:/sonar-2.7/war/sonar-server/WEB-INF/lib/jruby-rack-1.0.0.1.jar!/jruby/rack/boot/rack.rb:1:in `load’
    from :1

  • Hi Furkan,
    Please switch to the users mailing list ( http://www.sonarsource.org/support ) in order to troubleshoot your problems.

  • Hi,

    Any idea if manual review (on none violating codes) is possible in sonar 3.0?

    BTW, this tool is very helpful.

    Thanks,
    Stephen

  • Hi,

    Never mind. I found it already. It looks like i have to create an entry under “Manual Rules” for users to manually review code.

    Thanks,
    Stephen

Leave a reply