This post originated from an RSS feed registered with Agile Buzz
by Jared Richardson.
Original Post: Continuous Integration in the enterprise environment
Feed Title: Jared's Weblog
Feed URL: http://www.jaredrichardson.net/blog/index.rss
Feed Description: Jared's weblog.
The web site was created after the launch of the book "Ship It!" and discusses issues from Continuous Integration to web hosting providers.
Have you wanted to try out Continuous Integration but were afraid it wouldn't scale to your environment? Then this story is for you!
Will Gwaltney and I helped to introduce and roll out CruiseControl (a Java CI system) at SAS (the world's largest privately owned software company). Because we have five million lines of Java code and nearly 300 projects, some people were sure that a CI system would swamp the build infrastructure.
It did take a lot of resources to start up the system, but we dodged that by staggering the project startups.
Once CC was up and running, the load was amazingly light. Even with nearly 1,000 developers involved, we never had a situation that swamped the build environment. People being people, everyone finished up their work at a slightly different time, and that staggered the load.