On Fri, Feb 15, 2008 at 11:09:03AM -0600, Shawn Castrianni wrote: > I have my standalone ivy builds working great such that any > developer can build and retrieve dependencies. However, now I > am trying to get automated builds going for continuous integration, > scheduled nightly builds, etc. I was curious what people out > there are using. I always run into the problem of coordinating > the automated build systems build numbers and ivy's build numbers. > It would be great if they could be the same such that a developer > could look at the automated build website and see builds with > numbers that match the number in the ivy repository.
We don't use build numbers from the CI tool at all, we just do automated releases on demand. Here's an overview: http://www.dead-parrot.de/ivy/ > I also see overlap in functionality between ivy and automated > build systems with dependency management, publishing, and promotion. > I have all of that working with ivy and am wondering if I just > ignore those aspects of the automated build system in favor of > ivy? I'd go for the latter. Ivy does a much better job on publishing (and of course dependency management) then something like Cruisecontrol. Ciao, Kili
