You are viewing an old version (v. 6) of this page.
The latest version is v. 24, last edited on Aug 09, 2009
(view differences
|
)
<< View previous version | view page history | view next version >>
<< View previous version | view page history | view next version >>
Repositories need to be defined in order to set up configuration to build against source code in SCM. Before go further, we interpretate some concepts:
- repository snapshot
- repository revision
After a repository is defined, you can use it through below steps:
- checkout step
This step let you choose a repository to checkout. This is the only way to checkout files from SCM in QuickBuild. When this step runs, QuickBuild automatically takes a snapshot of the repository so that later steps (for example, the label step) operate on the same set of source code used for checkout. - label step
This step let you choose a repository to create label on. This step is useful if you want to label the SCM for the set of source code used for the build. This step will also take a snapshot of the repository. - take snapshot step
This step let you choose a repository to take snapshot. By running this step, a snapshot will be taken for the repository, and subsequent operations such as checkout, label will be done against that snapshot. Internally QuickBuild remembers the repository revision at the time of taking snapshots. Repository revision is interpretated differently for different SCM:- for subversion: it is the most recent revision of the repository
- for perforce: it is the highest changelist number of the repository
- for accurev: it is the latest transaction number of the repository
- for other repositories: it is the timestamp of the repository