XML based configuration

Easy to automate, orchestrate and manage. Review collected by and hosted on G2.com.

Need more documentation and, how-to-do tutorial.

Jenkins has become more popular than Cruise Control. Review collected by and hosted on G2.com.

We use cruise control to automate builds to different internal (and production) environments. We associate different branches with different environments and then when you click a button to build, you will build from the associated branch. Pretty straightforward and anyone can do it from a user standpoint. Review collected by and hosted on G2.com.

At least in our version, there's no confirmation window after you click to build. It'd be nice to confirm they were building to the right environment before executing the build. Review collected by and hosted on G2.com.

This software is easy use and this is how software should be. Review collected by and hosted on G2.com.

Not a thing. I love this software and look forward to using it. Review collected by and hosted on G2.com.

I like the community support and all the add-ins/plugins that exist. I have used CC for a couple of years and I have not faced a situation where the community can't help or where there isn't a plugin to simplify the life. Review collected by and hosted on G2.com.

I really dislike the use usage of XML to configure it. Sometime the config file can get really convoluted if you just add more and more projects in the same XML file. Even if there is a GUI tool and a schema checker I think that YAML or JSON would be a better tools for the job. Review collected by and hosted on G2.com.

- Simplicity

- Small codebase

- Pioneer in the area of automated-builds and CI

- Very easy to get started with Review collected by and hosted on G2.com.

- Lack of advanced features(multi-module builds, artifact management, jenkins like plugin ecosystem etc) and integrations

- Hasn't had a lot of steam in the last few years Review collected by and hosted on G2.com.

If you are in need of some sort of continuous integration system, there are quite a few options. You might heard of Jenkins, or Travis. But setting them up requires a lot of knowledge, lot of tools and a separate machine (or few).

If you need a simple solution, that is easy to install and that will just work, CruiseControl is the way to go. It does not have all the bells and whistles of the big systems, but it makes the job done.

I've used it quite a few times, when a client wanted a simple easy to setup system. Review collected by and hosted on G2.com.

It might be hard to configure and it might lack some features that the big systems provide, like Web interface. Review collected by and hosted on G2.com.

It's nice that cruise control is a mature, and popular CI platform that you can host yourself. This allows you to automate any number of build setups, as the configuration is 100% in your control. Review collected by and hosted on G2.com.

The same aspects that make it amazing, are actually it's downfall. I'd rather write my own software, than manage what at times turns into a picky piece of software. And, once we start talking hosted CI solutions, there's little benefit to sticking with cruise control at that point. Review collected by and hosted on G2.com.

Cruise Control was the best CI platform for a very legacy application (custom build process, app code in C), as it handled the unusual requirements very gracefully. Review collected by and hosted on G2.com.

I had some issues setting up the Ruby environment, but I think that was more of an issue with my custom environment rather than CruiseControl itself. Review collected by and hosted on G2.com.

At the time, I love the easy to setup and customize the tool. Including how I could use NAnt to automate my builds. Review collected by and hosted on G2.com.

At the time it was hard to integrate with other platforms such as SharePoint, Project Server. Also, the integration with Visual Studio IDE was missing functionality. However, I am sure that the new version is much better. Review collected by and hosted on G2.com.

I have used CruiseControl.NET at two companies that I have worked for and found it be an extremely powerful CI tool. Being an open source tool there is a level of technical expertise assumed when you install and configure it. Although the installation process installs and sets up the CC.Net service, there is level of manual configuration required to configure permissions. If you are technically capable then this won't be a problem, but if you lack IT skills then you may find this problematic.

CC.NET gives you huge amounts of flexibility in setting up your CI projects. You can even configure CC.NET so that you can build CC.NET itself as just another CI project. Pretty cool.

To create new CI projects you will need to manually edit the underlying XML files. If you are technically competent then this won't be a problem.

You get a lot of bang for your buck with the free version and I have never had to use the enterprise (paid) version. The free version can be used in heavy duty enterprise environments running multiple CI projects in large teams without any problem. Review collected by and hosted on G2.com.

Although never a problem for myself, CC.NET does require a level of technical competency to configure, both during the installation stage and in adding your CI projects. The UI and ease of use could be improved, but the level of flexibility that you get more than makes up for this.

I would like to see a gated build added to CC.NET i.e. where broken builds are rejected. If you check in code that breaks the build then you need to take remedial steps to correct it. In other CI tools such broken builds are rejected before they get to that stage. The build is instead safely quarantined where it can be corrected before it breaks your build process. Review collected by and hosted on G2.com.