This week I’m really proud to blog that we’ve released version 1.0 of CruiseControl.NET . It’s taken 3 years, but I believe it’s been worth the wait. One of the key reasons I work on the project is that I need a tool in my day-to-day work that fulfils the features we try to implement in CruiseControl.NET, and I’m always happy when I install it, setup a project and see it running.
CruiseControl.NET is an enterprise-class automated integration server. I believe we can say this quite confidently based on the fact we support 13 different source control tools, we have significant support for building and reporting multiple projects across multiple servers, our inter-project co-ordination, and lots more besides.
If you’re already a CruiseControl.NET user, I thoroughly recommend you upgrade to version 1.0. We’ve made significant updates to CCTray, have first-class support for MSBuild to better support you as you migrate to .NET 2, and a whole bunch of other updates.
So are we going to sit on our laurels now we’ve got the big one-oh out of the door? Far from it. We, along with the rest of the CruiseControl.NET community, are working hard on 1.1 already. Which reminds me, we wouldn’t be where we were if it weren’t for the massive support of a whole raft of CCNet users supplying patches and answering questions on the mailing lists. I can honestly say the project would not be close to where it is today were it not for CCNet user community, so a big thank-you to all of you out there.
You can download CruiseControl.NET 1.0 here. I hope you find it useful.