ad-hockery: /ad·hok'@r·ee/, n.
Gratuitous assumptions... which lead to the appearance of semi-intelligent behavior but are in fact entirely arbitrary. Jargon File

Building your app on Hudson with Multiple Grails versions

For my Grails plugins I generally write a test project (or more than one). I thought it would be useful to be able to run these against multiple versions of Grails on my build server so I can spot any incompatibilities with the versions the plugin is supposed to support.

Using Hudson this turned out to be pretty straightforward.

You will need all the Grails versions you want to test against installed on your Hudson box. I put them in /opt so replace that with wherever you have them in the steps below. Also, if you want the builds to run in parallel and will be running any functional tests you’ll need the Hudson Port Allocator plugin.

  • Start by creating a new job in Hudson and choosing "Build multi-configuration project".

  • The configuration dialog has an extra section "Configuration Matrix" where you can set up the different config combinations that will run. We’re just interested in varying the Grails version so check the "Axes" and create a new axis named "GRAILS_VERSION" with the different versions you want in the "values" box, e.g. "1.2.0 1.2.1 1.2.2 1.3.0.RC2"

  • Set up your source code repository and build triggers as you would for any other project.

  • If you want to run the builds in parallel and are running any functional tests you will need to make sure that Grails starts up on a unique port. In the "Build environment" section add a new "Plain TCP port" named "GRAILS_PORT". If you’re running anything else that needs a port such as a Selenium server you’ll need one for that as well.

  • Add an "Execute shell" build step. Unfortunately the Hudson Grails plugin does not allow you to use a variable to specify the Grails version so you’ll have to go old-school:

    export GRAILS_HOME=/opt/grails-latexmath:[$GRAILS_VERSION export PATH=$]GRAILS_HOME/bin:latexmath:[$PATH # assign Grails a unique port (you can skip this if you’re only running unit/integration tests) export JAVA_OPTS="$]JAVA_OPTS -Dserver.port=$GRAILS_PORT" grails clean grails upgrade --non-interactive grails test-app --non-interactive

  • Check "Publish JUnit test result report" in the "Post-build Actions" section and specify target/test-reports/*.xml as the "Test report XMLs"

When you run the Hudson job you should see it kick off one sub-job for each Grails version. Each will check out the project, upgrade it to the relevant Grails version and run the tests.

I have my plugin test projects triggered by the plugin build and have them grab the plugin zip itself from the archived artefacts in the plugin’s Hudson job. So I’ve added this before the grails test-app step:

grails install-plugin http://my.hudson.server/hudson/job/my-plugin/lastSuccessfulBuild/artifact/ --non-interactive

There’s a bug in Grails 1.3.0.RC2 that means you will need to split this into a wget followed by installing the zip from a file path rather than a URL. This is fixed in trunk so won’t be a problem in Grails 1.3 final.

If you’re using SVN I think you may need to revert any changes the grails upgrade has made to, etc. otherwise you’ll get merge conflicts on the next run. This does not seem to be a problem with Git.

Web Statistics