Having been nagged by gump for ages, I've been reluctant to use a continuous integration system, at least until a few days ago. Notwithstanding my conservative attitude, colleagues have patiently and convincingly explained that having an automated system building and testing my projects, was a good thing. Taking their word, I've installed Continuum in about 5 minutes and had it configured for SLF4J and logback projects in about 15, of which most were spent entering the correct "scm" incantations in the relevant Maven2 project (pom.xml) files.
I am still not completely sold to the idea of continuous integration (CI). As I understand it, in practice, continuum will check out the latest sources from source repository, build and run the test on the CI machine, and notify our team if anything goes wrong. Already at this early stage, Continuum feels like a new member of our team. The question is whether this new member is worth the maintenance. However, from the little experience gained in the last few days, Continuum seems to do what it is supposed to do without getting in the way. A new build is done only if the contents of the source repository change, and notifications are sent only when the latest build results differ from the previous one.
In short, once you've sold your soul to M2, continuous integration via Continuum is a piece of cake.
3 comments:
Ceki,
You might want to check our Parabuild server as well. Usually it takes ten minutes to the first build run.
Regards,
Slava Imeshev
Hi Ceki:
We have been using Continuum for a long time now. Could not imagine life w/out it.
Gonna try LogBack on our new project. Looking forward to it.
Regards,
Hi Rob,
If you do try logback, you might want try with the latest version, i.e. logback 0.9.1. This version is compatible with SLF4J 1.3 while logback version 0.9.0 is not. It won't make a difference if you don't use SLF4J. :-)
I'd be interested in your comments.
Post a Comment