In which version of cruisecontrol is composite Maven project build supported?
Thanks, /U -------------- Original message ---------------------- From: "Barrett Nuzum" <[EMAIL PROTECTED]> > Hi Aidan. > > We've done both on one of our engagements. > We first were building all dependencies too, then using a reactor build. > Lately, I've tended for the "fail fast" approach. > We have a large number of discrete projects in a single cruisecontrol > installation. > Increasingly, we're tending to let one fail to promote low coupling and high > isolation. > If, say, you have projects A-Z, and all depend on A, if something major gets > committed into A, but A is not yet rebuilt, let B-Z crash and burn quickly, > then > A will recompile, and B-Z will begin again. > > If you do the multi-module build, it works fine, but each build takes longer > to > handle. > Note also CruiseControl recently started supporting composite builders -- > that > is to say, you can define CruiseControl Project X as containing Maven > projects > A, B and C. It builds them in order. > > Multithreading your cruisecontrol builds, placing A on a very short interval, > and the other projects on a longer interval, can help alot too. > > Further questions along that line might be better suited for the > CruiseControl-user list. > > Hope that helps. > > Barrett > > :: > Barrett Nuzum > Consultant, Skill Development > Direct: 918.640.4414 > Fax: 972.789.1340 > > Valtech Technologies, Inc. > 5080 Spectrum Drive > Suite 700 West > Addison, Texas 75001 > www.valtech.com <http://www.valtech.com/> > making IT business friendly > > > ________________________________ > > From: Aidan O'Donnell [mailto:[EMAIL PROTECTED] > Sent: Thu 3/15/2007 6:27 AM > To: [email protected] > Subject: Cruiscontrol and Maven dependency management > > > > I am using cruisecontrol to build a multimodule project. > > The problem I am observing is that if projects A and B are checking in at > the same time and B depends on A the order that they are built in is not > set. > This means that if B builds before A then the build will fail. > > I have had a look for ways to manage the ordering of dependencies - one > thing I was thinking would be to get the bootstrapper to build A before B > (not nice). > The other thing I was thinking would be to do a complete build for the > project each time and that way get Maven to manage the ordering through the > parent POM (could be a timely process). > > Any suggestions? > > Aidan > > _________________________________________________________________ > Solve the Conspiracy and win fantastic prizes. > http://www.theconspiracygame.co.uk/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
