Continuous Integration Servers are often underspecified when it comes to hardware. In the early days of Automated Builds, the build server was quite often that old pc in the corner of the office, or an old server in the data center that no one else wanted. Developers weren't doing many builds per day, so it worked, it was probably slow but that didn't seem to matter much.
Fast forward 20 years, and the CI server is now a critical service. The volume and frequency of builds has increased dramatically, and a slow CI server can be a real problem in an environment where we want fast feedback on that code we just committed (even though it "worked on my machine"). Continuous Deployment only adds to the workload of the CI server.
In this post I'm going to cover off some ideas to hopefully improve the performance of your CI server.
The updates to Continua CI and FinalBuilder released today provide somewhat better integration between the two products.
Continua CI 1.5 introduces new Skip and Promote Conditions which allow you to dynamically control which stages run.
Roy Osherove posted this video explaining the difference between Automated Builds and CI (ie, FinalBuilder vs Continua CI)
The Branch Pattern Matching feature in Continua CI makes building Feature Branches simple.
Continua CI is our next generation Continuous Integration server product. This product will replace FinalBuilder Server once it's released.