I did some posts some months ago (Sonar – Cobol analysis with Jenkins, Open Source & Legacy code) with the idea to to show that you don’t need to be a J2EE guru or an Open Source expert to analyze Legacy code like Cobol (or ABAP) with Sonar and Jenkins.
And I see people going to my blog to look at these pages, which show some interest for this subject.
Now, as someone said recently: “We’ve got Sonar analysis well under way there. We’re contemplating putting Cobol under analysis as well, but I don’t understand the mainframe side and the Cobol-ers don’t understand the Jenkins & Sonar side”.
So, let’s try to help. This post (and following ones) has the objective to describe what you should know to implement a process of Cobol code analysis with Sonar and Jenkins.