{"id":1015,"date":"2010-01-07T20:13:53","date_gmt":"2010-01-08T05:13:53","guid":{"rendered":"https:\/\/www.kellyrob99.com\/blog\/?p=1015"},"modified":"2010-02-03T23:23:02","modified_gmt":"2010-02-04T08:23:02","slug":"bamboo-grails-and-git-for-continuous-integration","status":"publish","type":"post","link":"https:\/\/www.kellyrob99.com\/blog\/2010\/01\/07\/bamboo-grails-and-git-for-continuous-integration\/","title":{"rendered":"Bamboo, Grails and Git for Continuous Integration"},"content":{"rendered":"

Following up on my recent installation of the Atlassian<\/a> product suite at home, I had a really positive experience setting up Bamboo to work with several of my recent Grails projects. Bamboo has proven to be a powerful and essential tool at my day job and I’ve really been looking forward to putting it to work for my personal projects. I’ve also been using Git<\/a> for a repository lately, and while I have nothing but praise for my good friend svn, I have to say the ability to set up a new repository in 2 seconds flat is pretty damn convenient.<\/p>\n

Since neither Grails nor Git are by default supported by Bamboo, I grabbed a couple of plugins to enable my home continuous integration<\/a> system. Bamboo has a very sensible plugin model that allows for adding new capabilites with only a jar file in the right place and a server restart, and a fairly rich library of plugins<\/a>. It’s also encouraging to see a company that is committed to eating their own dog food – recently they’ve moved their plugin resources to Jira<\/a> studio as you can see on the Grails plugin home page<\/a>. This gives you as the consumer of the software access to the wiki’d documentation, any open issues, and even visibility into when source code changes are committed. I’m assuming that last is subject to whether or not the plugin source code is open source or not, but still – pretty nifty.<\/p>\n

The Grails plugin instructions speak for themselves in the 3 screen-shots on the one and only wiki page. Anything else you need to know is summarized in a one liner on the “Builder” tab when you select the Grails builder: “Use a new line to seperate Grails commands.” Gotta love clear, simple instructions. Drop the plugin jar into $BAMBOO_INSTALL_DIR\/webapp\/WEB-INF\/lib, restart Bamboo and configure a new builder for Grails<\/a>. Took a couple of minutes and knowing where my Grails install was located.<\/p>\nngg_shortcode_0_placeholder\n

A quick Google for “Bamboo git plugin” led to a bit of a hypertext chase that eventually ended up here<\/a>. Looks like this particular plugin has passed through the hands of at least a couple of maintainers<\/a>, but so far it’s worked exactly as advertised. And again, loving the dog food analogy, it’s nice to see a project enabling Git hosted on github. Thanks very much to Kristian Rosenvold<\/a> for running with the ball on this one! Again, drop the jar into $BAMBOO_INSTALL_DIR\/webapp\/WEB-INF\/lib and restart Bamboo. When creating a plan you will now have Git as a choice for a Source Repository. In my case I’m just using a plain file repository that resides on the build box, but it should work just as well with a remote repository.<\/p>\nngg_shortcode_1_placeholder\n

Setting up the Grails targets is similarly straightforward. Thanks to this article<\/a>, which describes the Grails setup on Hudson, and reminded me about the –non-interactive flag since obviously the build server isn’t going to be able to interact with the console. I’m also using a couple of Grails plugins to provide static source code analysis so my parameters also include -coverage and a call to the codenarc script.<\/p>\nngg_shortcode_2_placeholder\n

I had a little trepidation about how this would all turn out after reading this blog post<\/a>, but I’ve had much better results so far in my personal experience. It’s entirely possible that the key differentiator is wrapping Grails with Maven. It’s definitely not perfect, but it is getting better all the time<\/a>. Hopefully you have better luck in the future Neil!<\/p>\nngg_shortcode_3_placeholder\n

\"Reblog<\/a>