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.

Related Blog Posts
Android Development for iOS Developers
Android development has greatly improved since the early days. Maybe you tried it out when Android development was done in Eclipse, emulators were slow and buggy, and Java was the required language. Things have changed […]
Add a custom object to your Liquibase diff
Adding a custom object to your liquibase diff is a pretty simple two step process. Create an implementation of DatabaseObject Create an implementation of SnapshotGenerator In my case I wanted to add tracking of Stored […]
Keeping Secrets Out of Terraform State
There are many instances where you will want to create resources via Terraform with secrets that you just don’t want anyone to see. These could be IAM credentials, certificates, RDS DB credentials, etc. One problem […]
Validating Terraform Plans using Open Policy Agent
When developing infrastructure as code using terraform, it can be difficult to test and validate changes without executing the code against a real environment. The feedback loop between writing a line of code and understanding […]