Light-weight Continuous Integration Server for .NET
I want to set up a CI server for a personal project I'm doing with some colleagues as a learning exercise.
I've a virtual server we can use for the CI server but its rather low on resources (CPU/RAM and HDD).
Which .NET CI solution has the smallest footprint (I'm thinking Hudson)? I've seen plenty of threads comparing them, but nothing really on the resource us开发者_Go百科age.
I will confirm your statement for using Hudson. It is very easy to configure and use, it will take no more than an hour to have it up and running. For more serious projects (again open source) i will go with CruiseControl.NET. One constraint of using Hudson as CI is the small number of plug-ins that are available for .NET code. But. the major ones are there. Go with it.
Both are small enough to use on a contrained VM. The biggest consumer of resources is the actual compile of your projects, and the build artifacts they create. These are independent of the CI server you're using.
精彩评论