This project is read-only.

How to Determine if You Need a Rolling Build

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

Building immediately after every check-in is the simplest CI strategy and generally gives you the most rapid feedback. However, if check-ins occur rapidly enough to overwhelm the 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 find out 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 run continuously because the first build will not complete before the next check-in occurs, which starts another build. If check-ins continue to occur before each build is complete, this impacts the performance of the build server and will block other builds from being started, such as scheduled builds. Review the time window during which frequent check-ins occur and determine if CI builds are likely to impact the delivery of scheduled builds or other important team builds.

Additional Resources

  • For more information, see “Chapter 8 – Setting Up a Continuous Integration Build with Team Build” in this guide.

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


No comments yet.