During the hackathon at the Guardian where we first put together the LSug web app on Play2 / MongoDB / Heroku, we also wired the project up to Travis-CI.
Travis CI is a bit like Jenkins on the web, you simply point it to your github account and you can choose which projects you want Travis-CI to run on.
Whilst we pointed Travis-CI to the lsug-dojo/lsug-website repo on github, we didnt get round to adding a travis configuration file. Until now!
I just dropped in a new .travis.yml file into the lsug-website github repository and that triggered another travis-ci build. This time the test ran and passed!!
One benefit of using Travis-CI is to encourage the use of tests, it also gives information about the state of the github repository. This is especially useful when working with pull requests.
This is the first time I have used Travis-CI and it was really easy to configure. If you have any comments or ideas about this, please share them with the group or myself directly.