Oct 29, 2013

Testing Grails With a Travis Build Matrix

Continuous integration testing can be configured to create a build matrix to test multiple configurations of a project using a single build configuration.  This can be useful if you want to test a Grails application with multiple Grails versions, to test plugins with multiple Grails versions, or to test using varying configuration values.

The Travis CI build tool has a build matrix feature which allows you to specify multiple configuration parameters in the .travis.yml configuration file and runs the build against all possible combinations of these parameters. In the following example, I use the Groovy enVironment Manager (GVM) to change Grails versions between tests. I found this blog post which details how to set up GVM for Travis and updated this approach to force the GVM install command to return success instead of the workaround given there. The env block in the .travis.yml specifies the different environment parameters which will be passed to each test run to create the build matrix:

The example build result below shows the different Grails version on the right used for each build. The source code for this example project can be found on Github.

Example Travis build matrix output of a Grails project build using GVM

More information about configuring a build matrix for Travis can be found in the Travis CI documentation.

About the Author

Object Partners profile.
Leave a Reply

Your email address will not be published. Required fields are marked *

Related Blog Posts
Waypoint and JVM
What are we doing here? We’re going to to run Waypoint to build a Clojure web application, deploy it, and release it on a URL. Along the way, we’re going to see how it interacts […]
Understanding Mutual TLS Options in the Public Cloud
When delivering an API over the public internet via a cloud provider, some organizations and frameworks require mutual TLS verification as a part of the interaction for that API. Mutual TLS can be used to […]
Performance Test Liquibase Update
When doing a liquibase update to a database if you’re having performance issues, it can be hard to find out which updates are causing problems. If you need to measure the time to apply each […]
TICK Stack Monitoring for the Non-Technical
TICK – Telegraf, Influx, Chronograf, and Kapacitor – is a method of monitoring your systems and applications. In this article, I discuss in non-technical terms what the difference is between TICK and Prometheus Grafana A […]