In this series of posts on the installation and configuration of SonarQube, we have seen how to realise a first analysis of code with the SonarQube Runner.
Today we will see how to install and configure Jenkins that we will use (later) to manage all our analysis.
This is also an opportunity to detail the resolution of some problems specific to our environment, and incidentally to see how to detect these problems with the Tomcat server, which we have installed previously.
We have previously installed the SonarQube portal with Tomcat, and the SonarQube Runner, which will enable us to achieve our first analysis today.
In the installation folder of the SonarQube Runner, we cand find three directories:
Before configuring it, let‘s pause a moment to think about the organization of our analysis environment.
The SonarQube Runner allows us to perform source code analyzes without using tools such as Ant or Maven.
These toos are well known from J2EE (or any other new technology) development teams, but let’s remember that our objective in this serie about the installation of SonarQube, and more generally in our blog, is to allow anyone to perform code quality and applications analyzes, without requiring any knowledge of these new technologies. Continue reading
I am a little late in writing this series of articles on installing and using Sonar: it was Semana Santa in Spain, a week of holidays and so I wanted to enjoy it for the first time this year. And as the next week has been short but intense, I could not catch up.
Fortunately, we’re done with long articles on Oracle, and as the installation of Sonar is not very complicated – if you take the time to carefully observe every step – I hope to write posts shorter but more frequent. Continue reading