When to Use SNAP Builds

You might want to implement a SNAP build in two places:

• In one of your Virtual Build Labs or private branches (as talked about in Chapter 2, "Source Tree Configuration for Multiple Sites and Parallel (Multi-Version) Development Work") prior to checking into the mainline source tree. Some groups at Microsoft use the SNAP tool as a pre-check-in test to make sure that all changes in a particular project integrate with other changes in other components of the project. In some ways, this replaces a build team for a particular VBL. As recommended later, you should not view this tool as replacement for builders. You still need someone to administer or monitor the SNAP process.

• As a gateway to the mainline source tree. Other groups at Microsoft use this tool for their main build process. In fact, the "Lessons Learned" sidenotes are from the NetDocs team, who used SNAP as their main build process.

Alternatively, you can implement a SNAP build in both places. The implementation depends on the complexity of your build process and product.