Message-ID: <154443909.9377.1409459331612.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_9376_55846064.1409459331612" ------=_Part_9376_55846064.1409459331612 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
It is recommended to run project analyses on a regular basis to get the = best from the SonarQube platform. Continuous Integration servers are the pe= rfect tools to do so.
Install and configure the SonarQube Jenkins plugin.
Install and configure the = SonarQube Hudson plugin.
The difficulty in Continuum is to be able to synchronize an
l goal with the
sonar:sonar goal because it is necessar=
y that an
install goal is run before the SonarQube collect sta=
rts (See Analyzing Source =
Code for more information).
Since Continuum does not provide mechanism to = trigger a build from a build, there are two options: either running
nstall goals regularly (for example every hour), or trigger a comple=
te command such as:
In case you decide to run
install commands regularly, here =
is the setup you can do for the SonarQube build:
For multi-module projects, make sure that the --non-recursive build definition argument is NOT set.
In CruiseControl, use the | to run t= he
install and the
sonar:sonar goals in two diffe=
rent processes. The command to be run should look like:
These are the build configuration steps you need to do for the build:
In build runner config, select Maven2, with the goal
Additional Maven command line parameters: