All geek questions in one place

CruiseControl or CruiseControl.NET

I am using the latest version of CruiseControl.NET (1.6.7981.1). It works quite well, but the web dashboard is not the largest, and I don’t like the way the service refuses to start if any of the project files configured XML incorrectly.

What are my options? How about using a basic CruiseControl? Will he play well with MSBuild? Will it format MSBuild results reasonably, like CruiseControl.NET MSBuild Report? I see that he has not had issues since September 2010. Yikes. In fact, is it completely baked?

+1
source share
2 answers

CC.NET is really better than CruiseControl, and lightweight.

If you need to change, first write down your requirements and limitations of such a continuous integration tool.
If you just need something “nicer” and easier to use, then consider switching to Jenkins , since the configuration is mainly done using the web interface.

If you need custom reports, custom emails, or custom stats, then continue with CC.NET.

And remember that you should always use CCValidator.exe located in the CC.NET installation folder to check your configuration files.

Switching from one CI tool to another is easy, as you already have all the scripts to execute.

+2
source

As a longtime cc.net user, I would recommend switching to Jenkins or TeamCity. I really like TeamCity, but Jenkins is trivial to set up and run.

+3
source

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

More articles:


All Articles