A distributed build is when a build is spread across multiple machines. It does allow concurrent builds - but it doesn't handle working with other servers very well.
If CC.Net is working fine for you now, and you have no issues with it, I'd stick with it. You've obviously had plenty of experience with it, whereas changing to Cruise will involve learning a new system. Craig On Mar 6, 12:13 pm, SMS <[email protected]> wrote: > Sorry for confusing in the names. > > Craig, that distributed build question was intended towards you. > > Thanks > > On Mar 5, 5:11 pm, SMS <[email protected]> wrote: > > > > > Thanks Mark and Craig for your quick responses. > > > First of all, my company needs a free version. I do understand, that > > Cruise is free uptill two agents. What exactly a agent is doing in > > Cruise? > > > Mark, what did you mean by "CCNet does not provide distributed build"? > > Does that mean that many builds running concurrently? > > If yes, this is not the requirement in my case. We have worked very > > well with queued builds in CCNet uptil now. Also, security is also not > > our priority. > > So, do you think, there is no need to go to Cruise, when CCnet is > > sufficing our needs? > > > Thanks. > > > On Mar 5, 4:56 pm, Mark Ryall <[email protected]> wrote: > > > > Funny you should ask this question - I need to answer this question for my > > > current client. > > > There are actually 4 continuous integration products associated with > > > thoughtworks that feature the word 'cruise'. It seems that this fact can > > > cause a great deal of confusion - they are all similar in concept but > > > completely different in implementation. > > > >http://ccnet.thoughtworks.com-Theopen source .net implementation that you > > > all know and love (ideally suited for building .net projects) > > > >http://cruisecontrol.sourceforge.net-Theoriginal open source java > > > implementation that started it all (ideally suited for building java > > > projects) > > > >http://cruisecontrolrb.thoughtworks.com-Amore recent open source ruby > > > implementation (ideally suited for building ruby projects) > > > >http://studios.thoughtworks.com/cruise-continuous-integration-Acommercial > > > continuous integration tool that was released last year > > > > There main features of the commercial version of cruise are > > > here:http://studios.thoughtworks.com/cruise-continuous-integration/feature... > > > > I'd suggest that you ask your coworkers to demonstrate their perceived > > > benefit of using cruise (the specific problems that will be solved by > > > using > > > it instead of the open source version). There are a great many things > > > that > > > you can do with the commercial version that would require a lot of effort > > > using the open source versions (build pipelines, parallellisation, testing > > > on multiple platforms etc.). The question is whether your team would > > > benefit from doing any of those things. > > > > Mark. > > > > On Fri, Mar 6, 2009 at 9:20 AM, SMS <[email protected]> wrote: > > > > > Hello, > > > > > I have been using CCNET for more than 3 years now. I have been pretty > > > > satisfied with how it works. > > > > I just got to know about from Cruise (again by ThoughtWorks). > > > > What is the exact difference between these two products? > > > > Why should I stick to CCNet when Cruise has come out in market? > > > > > I need some substantial answers since I got answer to my c-workers who > > > > have been insisting that we should start using Cruise instead of > > > > CCNet. > > > > > Thanks.- Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text -
