We're been using CruiseControl here for a very long time. It works well for a handful of larger projects, but our move to Maven has enabled us to break the larger projects into more agile smaller projects. This has made some of the drawbacks of CruiseControl more apparent. CruiseControl does have a Maven integration that's acceptable but could be better. I would like a tool that can do more without having to restart the tool completely. I'd also like to see something that better recognized and handled inter-dependencies between projects.
Because of the drawbacks I've seen with CruiseControl, I will be looking at other possible solutions in the near future. Right now I'm leaning toward Luntbuild because it is a bit more mature that Continuum, but I'll definitely be giving it a try as well. When you do decide on a CI tool, I'd be very interested in knowing which one you chose and why. ..David.. -----Original Message----- From: Wim Deblauwe [mailto:[EMAIL PROTECTED] Sent: Thursday, September 08, 2005 5:22 AM To: Maven Users List Subject: Advised Continous Integration tool? Hi, I'm looking into CI tools and I wonder what other already use: CruiseControl, LuntBuild, DamageControl, maven's own Continum, ... What are your experiences with CI tools and Maven 1.x? What are the advantages/disadvantages? I heared CruiseControl is not so easy to setup compared to LuntBuild. Anyone caring to share his experience? regards, Wim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
