Dashboard > Pulse v2.1 > ... > Concepts > Checkout Schemes
  Pulse v2.1 Log In | Sign Up   View a printable version of the current page.  
  Checkout Schemes
Added by Jason Sankey, last edited by Jason Sankey on Aug 25, 2009
Labels: 
(None)

Pulse Manual Index

Checkout Schemes

A checkout scheme specifies how pulse™ should bootstrap, or prepare a working directory, for your recipes. The available checkout schemes are:

  • Clean Checkout: the default, where a new directory is created for every build and populated via a clean checkout from your SCM.
  • Clean Update: the code is incrementally updated from your SCM into a persistent directory, and then copied to a new clean directory that is used as a base for the recipe.
  • Incremental Update: all recipes for a project on an agent reuse the same persistent directory, where the code is incrementally checked out and the recipe is run in place.

We recommend using a clean build every time if it is fast enough to be practical. For larger projects, incremental building may be much faster.

Zutubi wiki is Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.2.10 Build:#528 Nov 29, 2006) - Bug/feature request - Contact Administrators