This documentation relates to QuickBuild 4.0.x
Select here if you are using a different version

Log In

Repository Path

Added by Robin Shen, edited by Robin Shen on Oct 15, 2011

You are viewing an old version (v. 2) of this page.

The latest version is v. 6, last edited on Oct 15, 2011 (view differences | )
<< View previous version | view page history | view next version >>

Repository path is used to refer to file in SCM systems. Example repository urls for different SCM systems:

Subversion: the path is relative to Subversion root, WITH a leading "/".
```
/my-app/trunk/pom.xml
```
Since this relatives to Subversion root, it will remain unchanged whether the checkout url defined in a Subversion repository is svn://localhost/my-app or svn://localhost/my-app/trunk.

CVS: the path is relative to the CVS root, WITHOUT the leading "/"
```
my-app/trunk/pom.xml
```
Since this relatives to the CVS root, it will remain unchanged whether the checkout module defined in a CVS repository is my-app or my-app/trunk

Perforce: the path should be an absolute path in the Perforce server, including the depot part
```
//depot/my-app/trunk/pom.xml
```

Visual SourceSafe: the path is an absolute path in sourcesafe database, starting with "$/"
```
$/my-app/trunk/pom.xml
```
Since this relatives to the sourcesafe root, it will remain unchanged whether the checkout project defined in a VSS repository is $/my-app or $/my-app/trunk.

Accurev