Lightweight continuous integration server for .NET.

I want to set up a CI server for a personal project that I am doing with some colleagues as a training exercise.

I have a virtual server that we can use for the CI server, but its rather low resource (CPU / RAM and HDD).

Which .NET CI solution has the smallest footprint (I think Hudson)? I have seen many threads comparing them, but nothing is worth using resources.

+3
source share
2 answers

Both are small enough to be used on a limited virtual machine. The largest consumer of resources is the actual compilation of your projects and the build artifacts they create. They are independent of the CI server you are using.

+3
source

I will confirm your expression for using Hudson. It is very easy to configure and use, it will take no more than an hour to launch and work. For more serious projects (again open source) I will go with CruiseControl.NET. One of the limitations of using Hudson as a CI is the small number of plugins available for .NET code. But. there are basic ones. Go with him.

+4
source

Source: https://habr.com/ru/post/1777654/


All Articles