Set Up Proof Build

Version 1 by Robin Shen
on Dec 24, 2009 08:09.

 
compared with
Version 2 by Robin Shen
on Nov 07, 2010 11:14.

Changes from 2 to 3 >>
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 2 changes. View first change.

 Proof build setup is different for different SCM:
 * [Set up proof build for CVS|Working with CVS#proof build]
 * [Set up proof build for ClearCase|Working with ClearCase#proof build]
 * [Set up proof build for Perforce|Working with Perforce#proof build]
 * [Set up proof build for StarTeam|Working with StarTeam#proof build]
 * [Set up proof build for Subversion|Working with Subversion#proof build]
  Proof build support is enabled per SCM. Refer to below links on how to set up proof build for different SCMs:
 * [Bazaar|bzr proof build]
 * [CVS|cvs proof build]
 * [ClearCase|clearcase proof build]
 * [Git|git proof build]
 * [Mercurial|hg proof build]
 * [Perforce|p4 proof build]
 * [StarTeam|starteam proof build]
 * [Subversion|svn proof build]
 * [Visual SourceSafe|vss proof build]
  
 For SCMs not listed here, proof build is not supported.
  
 After proof build has been set up, you may need to tune _node match condition_ of corresponding steps so that multiple builds in the same proof build configuration can run concurrently. It is critical to get fast proof build feedback when multiple developers are running proof build against the same configuration. Refer to [build concurrency] for details on how to tune the _node match condition_.
  Proof build for other SCMs not listed here is currently not supported.