Scaling and Managing CruiseControl.NET Configuration

Short Form


Have a bunch of CruiseControl.NET build servers? Drowning under the weight of duplication? Is copy and paste your go-to maintenance tool? Come learn how we manage more than 11 build servers with no configuration duplication and easy maintenance.


We started using CruiseControl.NET on three build servers. The configuration between the servers was not shared. Maintaining the configuration was painful and involved a lot of copy and paste. Aargh!

Fast-forward to today. We now have 11 build servers, with an additional five that rotate in and out of service. All of them run CruiseControl.NET from the same repository in version control. Several servers are owned by independent teams. We’ve managed to eliminate any duplication between services and make it trivially easy for teams to manage their builds.

Speaking experience

I give training at work.