26.04.2015 Views

Team Development with Visual Studio Team Foundation Server

Team Development with Visual Studio Team Foundation Server

Team Development with Visual Studio Team Foundation Server

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Additional Resources<br />

• For more information, see “Chapter 8 – Setting up a Continuous Integration Build<br />

<strong>with</strong> <strong>Team</strong> Build” in this guide.<br />

• For more information about setting up a CI build, see “How To – Set Up a Scheduled<br />

Build <strong>with</strong> <strong>Visual</strong> <strong>Studio</strong> <strong>Team</strong> <strong>Foundation</strong> <strong>Server</strong>” in this guide.<br />

• For more information about how to use the <strong>Visual</strong> <strong>Studio</strong> <strong>Team</strong> System CI solution,<br />

see “Continuous Integration Using <strong>Team</strong> <strong>Foundation</strong> Build” at<br />

http://msdn2.microsoft.com/en-us/library/ms364045(VS.80).aspx<br />

• To download the <strong>Visual</strong> <strong>Studio</strong> <strong>Team</strong> System CI solution MSI, go to<br />

http://download.microsoft.com/download/6/5/e/65e300ce-22fc-4988-97de-<br />

0e81d3de2482/ci.msi<br />

• For more information about agile development and CI in TFS, see “Extend <strong>Team</strong><br />

<strong>Foundation</strong> <strong>Server</strong> To Enable Continuous Integration” at<br />

http://msdn.microsoft.com/msdnmag/issues/06/03/<strong>Team</strong>System/default.aspx<br />

How to Determine if You Need a Rolling Build<br />

Building immediately after every check-in is the simplest CI strategy and generally gives<br />

you the most rapid feedback. However, if check-ins occur rapidly enough to overwhelm<br />

the build server, you should use a rolling build approach where you build after a specified<br />

number of check-ins or after a specified time period. To find out if you need to use a<br />

rolling build, determine the following:<br />

• Length of your team build in minutes<br />

• Average frequency of check-ins in minutes<br />

• Time window during which frequent check-ins occur<br />

If the length of the build is longer than the average frequency of check-ins, your builds<br />

run continuously because the first build will not complete before the next check-in<br />

occurs, which starts another build. If check-ins continue to occur before each build is<br />

complete, this impacts the performance of the build server and will block other builds<br />

from being started, such as scheduled builds. Review the time window during which<br />

frequent check-ins occur and determine if CI builds are likely to impact the delivery of<br />

scheduled builds or other important team builds.<br />

Additional Resources<br />

• For more information, see “Chapter 8 – Setting Up a Continuous Integration Build<br />

<strong>with</strong> <strong>Team</strong> Build” in this guide.<br />

How to Determine Your Rolling Build Time Interval<br />

It is important to determine the rolling build time interval to ensure an efficient build<br />

process. You will want a timely build while at the same time not overloading the build<br />

process.<br />

To determine the ideal rolling build interval, divide the average frequency of check-ins<br />

by the length of your build. For example, if you have a build that takes 10 minutes and

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!