This project is read-only.

Use a Rolling Build if CI Builds Are Adversely Impacting Build Server Performance

- J.D. Meier, Jason Taylor, Alex Mackman, Prashant Bansode

Building immediately after every check-in is the simplest CI strategy and will generally give you the most rapid feedback. However, if check-ins occurs rapidly enough to overwhelm your build server, you should use a rolling build approach where you build after a specified number of check-ins or after a specified time period. To decide if you need to use a rolling build, determine the following:
  • Length of your Team Build in minutes
  • Average frequency of check-ins in minutes
  • Time window during which frequent check-ins occur

If the length of the build is longer than the average frequency of check-ins, your builds will run continuously because the first build will not complete before the next check-in occurs, which will start another build. If check-ins continue to occur before each build is complete, it will impact the performance of your build server and will delay other builds, such as scheduled builds. Review the time window during which frequent check-ins occur and determine if CI builds will impact the delivery of scheduled builds or other important Team Builds.

Additional Resources

  • For more information about setting up CI builds, see “Chapter 8 – Setting Up an Continuous Integration Build with Team Build” in this guide.

Last edited Jul 26, 2007 at 6:19 AM by prashantbansode, version 1


No comments yet.