views:

1884

answers:

9

Any ideas as regards alternatives to Cruise Control .NET?

+2  A: 

CI Factory is easy to setup and use

Kb
Didi you use CCNET before? Can you explain your point in details?
omoto
@omoto: Each instance oof CI Factory has its own CCNet. So CI factory is really a better CCNet
Kb
+6  A: 

You could try Teamcity http://www.jetbrains.com/teamcity/ It's primarily focussed at java but can run .net builds too with nant. It's easier to set up than cc.net but a bit less flexible.


Mike Two pointed out TeamCity will do msbuild too.

Mendelt
It will also do .NET builds using MSBuild or just point it at your visual studio solution. It has a few more tools for java but I think that is mostly because there are more java tools out there in the universe.
Mike Two
@Mike Two, thanks, I didn't know it did msbuild. Teamcity has been built in Java, that might explain the slight bias towards that language :-)
Mendelt
+17  A: 

I'm a .NET developper and I love TeamCity it's really a great tool ! Easy to configure, to install, to work and it has a pre commit functionnality. I've stop CC .NET because I spent to much time debugging build scripts for basic behavior. ps : I have not tried to configure CCNET with CCNETConfig.

Nicolas Dorier
Thanks for your point, I'm already downloading TeamCity :)
omoto
You-re welcome, you'll see in less than 30 minutes, your project will be configured to run tests, build scripts, compile, or pre-commit the code before each check in.
Nicolas Dorier
Does anybody know how to configure TeamCity with MS Test.I have problem with path to .trx file.
omoto
My config for MSTest is %system.MSTest.9.0%, LocalTestRun.testrunconfig, myFile.vsmdi, MyTestListName that's all, and it works
Nicolas Dorier
+3  A: 

The answers to this question might help some. http://stackoverflow.com/questions/195835/cruisecontrol-net-vs-teamcity-for-continuous-integration

But the big ones out there are CC.NET, TeamCity from JetBrains, and Team Foundation from Microsoft. There are others but I'm not as familiar with them.

CC.Net is the oldest and has a large community. It is also the only one of the three I listed that is open source. It will be interesting to see how long it lasts since ThoughtWorks has released a new product called Cruise.

TeamCity is not open source but has an extensive api and a growing community. I use it now after years with CC.NET

Team Foundation Server is huge and expensive. It works and has some nice integration with work item tracking but you need a ton of hardware and software to run the thing.

Mike Two
Cruise is independent of the open source CruiseControl efforts. CruiseControl, CC.NET and (afaik) cruisecontrol.rb will continue.
Jeffrey Fredrick
That is still to be determined. In particular the effort toward CC.NET was dropping off and there was talk of stopping after Cruise came out. The java version has enough momentum that it will continue, and rb might also. Cruise is independent in the sense of people and effort, but not code or ideas.
Mike Two
+3  A: 

I blogged about this awhile back and I had a set of tools for it listed - check it out - link.

The blog post is about continuous integration but I did list some tools at the bottom - they are all open source and free. Frankly I haven't yet felt the need to buy a too for CI since there are some nice open source ones out there.The tools themselves are written in Java or .NET but can be used to set up CI for any language...

Thoughtworks (the company where Martin Fowler (the guy who introduced CI) works) has a commercial tool and open source versions as well.

Teamcity is big and I think has a lot of momentum but I haven't used it. I believe they have a free version you can use till you reach your limit.

Atlassian has one called Bamboo - I haven't used this either.

Hudson is a popular one written in Java. It has some nice features.

CI Factory is essentially an enhanced version of Cruise Control .NET

There are some nice answers in this link as well (Mike pointed this out in the earlier answer) - http://stackoverflow.com/questions/195835/cruisecontrol-net-vs-teamcity-for-continuous-integration

Nikhil
+10  A: 

You know about the giant CI Feature Matrix?

Jeffrey Fredrick
That's very helpful, and now bookmarked. +1
Randolpho
Thanks.There goes another working day :-( :-)
Avi
+2  A: 

I just love http://www.finalbuilder.com , I use their system for continious integration and all my build operations. Easy to use/debug and love their web-inteface.

Andy
+about 35 for FinalBUilder - invaluable took and I've yet to find anything that it can't do...
Matt
or even tool...!
Matt
+1  A: 

Check out this TeamCity screencast (the first 1/3):

Kona: Continuous Integration and Better Unit Testing

boj
+3  A: 

In the Java world, Hudson is quickly replacing CruiceControl as the preferred continuous integration tool for many, and it looks like things are not that different on the .NET side. For a nice introduction, check out this answer about using Hudson as a .NET build tool.

Edit: for more details on why should Hudson be better than CruiseControl(.NET), see my answer in a "CC vs Hudson" question.

Jonik