Hi Nathaniel, I suspect you'll get slightly biased answers here, being a ccnet list, but I would say:
Most of our projects are c#, but we also used ccnet to build documentation, create and populate databases from script, manage backups, analyse the codebase (simian) and to prepare our releases (build entire package from a set of tasks and deploy to uat system - from where it can be easily copied to live). We've found it to be a really flexible tool for scheduled and/or triggered processes in general. On the java front, I don't see that it would be very hard to integrate with ccnet - even if you end up using nant and writing a series of command line calls to the compiler, junit, etc - as long as you can get the output in a format which can be used (e.g. failure/success return code and at least output to stdout which can be caught in a log). Mind you, I know nothing of Maven (haven't used Java for a loong time). If the Java stuff needs to be built on unix boxes, then im out of water as well, as we use ccnet in a windows-only environment... Still. I'd give it a shot! Best of luck with it all! Matt 2008/10/6 Nrichand <[EMAIL PROTECTED]> > > Hy all, > > I'll go to a new project where the front office is developed in C# and > the Back Office in Java. > They chose CCnet for the CI server and want to integrate the java part > here. > Is this the right choice? > > One server is easier to manage. > But both server (Cruisecontrol and CruiseControl.net) have different > features and CCnet doesn't handle Maven and poorly Ant Build... > > What is your point of view? > > Thanks by advance, > Nathaniel >
