Setting up Grails code quality tools with local Sonar
21 Nov 2013, 2 minute read
Code violations (poor coding constructs)
Despite a load of Google results suggesting it would be impossible (or at least quite hard), it turned out to be relatively straightforward.
You can check it’s running at http://localhost:9000/, but you can use nginx to give you a prettier URL (I’ll cover that in a later post). While you’re at it change the default “admin” user password from “admin”.
Adding Maven to the Grails project to run Sonar
We need to set up Maven to post the results to Sonar. Because we don’t want local machine configuration included in the project Git repository, let’s add the database connection details to our local Maven settings file (~/.m2/settings.xml) which may not exist yet, so just create it with the following contents:
The important elements to check are:
sonar.host.url, which should be “http://localhost:9000” unless you’re proxying through nginx
sonar.jdbc.url and ensure that database actually exists (I use postgres, pick your own flavour)
You then need to add a pom.xml file to the project you want to analyse:
Here the points of interest are:
sources, ensuring all your source code is under inspection
You can test for success by running “mvn sonar:sonar -DskipTests=true” in the same directory as the pom.xml file. All things being equal it will show “Build Success” on the command line and populate your Sonar installation with a project.
When I next get a few minutes I’m going to get this set up in Jenkins and tie it all together with nginx, and possibly write about how we’re automating it all with Boxen. Until the next time…
Was this post useful? Why not help others find it by sharing on twitter. While you're there, get in touch and let me know what you think!