ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles Scokart" <>
Subject RE: IvyCruise replacement
Date Wed, 02 May 2007 08:08:08 GMT
I'm using cruisecontrol with +/- 60 modules.  

I just rebuild all modules every time that a change is detected in any
module.  The build take now 20 minutes when it is successful (but often
fails after less than 5 minutes ;-).  This is acceptable for us.

The benefits is that it is simpler to setup.  Moreover, I can publish the
artefact to a snapshot repository only at the end of a full build so that
I'm sure that the snapshot repository is always consistent.

However, this approach doesn't scale very well...  In my case, most of the
developers are working simultaneously on most of the modules.  But if it is
not the case, you have probably to take an other approach.


> -----Original Message-----
> From: Tim Diggins []
> Sent: mardi 1 mai 2007 12:48
> To:
> Subject: IvyCruise replacement
> Hi -
> I'm considering ivy as a mechanism to express and manage dependencies
> (currently only expressed in ant tasks), but as one of my main drivers
> is to fix my continuous-build problems, am wondering what people do who
> use ivy and cruisecontrol at present, given that ivycruise is apparently
> not active and not working with latest cruisecontrol?
> What do people do?
>  * not use cruisecontrol?
>  * live with the failures when things get built in the wrong order?
>  * Use some other kind of modificationset and just update all
> dependencies each build?
> any perspectives helpful
> ]
> thanks
> Tim
> --
> ---------------
>   Tim Diggins

View raw message