Hi Daniel, If I need continuous integration from Source control then I will require both ant and CruiseControl. Otherwise I can schedule a scrip (ant build script) to run at specific time.
Regards, Pranathi On Dec 18, 3:25 pm, Daniel Hommel <[email protected]> wrote: > On Thu, 18 Dec 2008 12:03:38 -0800 (PST) > > > > > > Pranathi <[email protected]> wrote: > > > Hi Daniel, > > > We have different solutions developed in Java and .NET. We > > want to use cruise control > > as continuous integration tool for combing our .NET and Java > > applications. We will have one build server > > and install cruisecontrol, IDE for .NET solutions, JDK for Java > > solutions. If we have to use ant for > > Java then we might as well use the same for .NET applicaitons too, > > then we might not require cruise control. > > We need to go for one tool either nant/ant or cruise Control. > > > Thanks, > > Pranathi > > Hi Pranathi, > > in my opinion there is a important difference in this both types of > tools: > -Ant and NAnt (and MSBuild, Maven etc) are build tools > -CruiseControl(.NET/.rb or the Java one) is a continuous integration > tool, not a build tool in the sense of the above > > Build tools are used for automating a build (compile, test, deploy etc). > Continuous Integration tools are used to continuously run the automated > builds and report the results. To me these are two different jobs and i > do not see a problem with using Ant or NAnt with CruiseControl. I guess > most of the people are using it that way. Do you have reasons for > stricly using only one tool for both jobs? > > regards, > > Daniel- Hide quoted text - > > - Show quoted text -
