Sonar in the news
Welcome to the roundup of blog posts and pages that mentioned Sonar last month…
June was fully dedicated to Jean-Pierre Fayolle ;-)
Cobol source code analysis with Sonar and Jenkins
By Jean-Pierre FAYOLLE, 9 June 2012
Let’s continue our serie about the analysis of Cobol code, with the objective to demonstrate that it is simple and easy to initiate a process of evaluation of the quality of this Legacy code, without being a Mainframe expert. You already have a platform of code analysis with Sonar and Jenkins. If this is not the case, an earlier serie of posts will explain you how to install these tools…
By Jean-Pierre FAYOLLE, 17 June 2012
We have seen in our previous post how to analyze Cobol code with Sonar and Jenkins. But in fact we have not used all the existing Cobol rules. Why? Some rules are disabled because they are specific to a particular context and then require some setup. For example, naming rules are not standardized in Cobol, and will often be different between different departments or even between teams from the same department. So we need to manage different Quality models corresponding to different set of rules, depending on the project. Sonar gives us that opportunity, thanks to the ‘Quality profiles’ which include active rules during a code analysis…
Sonar – Cobol rules
By Jean-Pierre FAYOLLE, 18 June 2012
The previous posts about the preparation and analysis of Cobol code with Sonar and Jenkins drew some anxious comments about the results of the analysis and the rules available in the Sonar dashboard. Do these results allow an evaluation of the quality of Cobol applications? What value do we deliver to teams, stakeholders and management? And for those who are not familiar with the Mainframe world, what are the ‘best / bad practices’ in terms of Cobol code?
Sonar – Your own Quality Model
By Jean-Pierre FAYOLLE, 23 June 2012
A rule is known or it is not. A ‘best practice’ is applied or is not. But if it is not applied, is it because it is not applicable? You must present the results of your initial Cobol analysis and of course, you want them to be as most relevant as possible in order to prove their value to the project teams, providers, stakeholders, etc.