The instructions on this page describe how to configure a CVS source repository for either a Plan or a Job. | On this page: |
Configuring a CVS Source Repository
Navigate to the source repository settings for a Plan or Job, as described on Specifying the Source Repository for a Plan. Choose to add a new or edit an existing repository and select CVS in the Source Control drop-down.
CVS gives you the following options:
CVS Root | Type the full path to your CVS repository root (e.g.
| |
Authentication Type | Password | Choose this option if you want to authenticate with a username and password. |
SSH | If you choose to authenticate via SSH, you will have to provide the following details: Private Key — The absolute path of your SSH private key | |
Quiet Period | This setting is used to avoid starting a build while someone is in mid-checkin. Bamboo will only initiate a build for this plan when no more changes are detected within the Quiet Period following the last known change. Type the number of seconds Bamboo should wait. Please note that this parameter is mandatory for CVS, as CVS allows partial checkouts. (Only available when configuring an existing Plan) | |
Module | Type the name of the CVS module that contains the source-code.
| |
Version of module | You can choose HEAD or a specific Branch/Tag. If you choose Branch/Tag, you will have to provide the name of the branch or tag.
|
Common Repository Configuration
Force Clean Build | You can force Bamboo to remove the source directory and check it out again prior to the Plan/Job build being built by selecting this option. Please note that this will greatly increase the time it takes to complete a build. | ||
Clean working directory after each build | You can force Bamboo to remove the source directory after the Plan/Job is completed building by selecting this option. Please note that this may increase build times but saves on disk space. | ||
Include/Exclude Files | You can specify a particular inclusion or exclusion pattern for file changes to be detected. If you select an option other than 'None', the following field will appear: File Pattern — The regular expression for file changes which you wish to include/exclude. The regex pattern must match the file path in the repository. Visit sub page for a few examples. | ||
Web Repository | Generic Web Repository | Web Repository URL — If your source repository can be accessed via a web browser, you can specify the URL of the source repository here. If you specify a Web Repository URL, then links to relevant files will be displayed in the 'Code Changes' section of a build result. Web Repository Module — The repository name of the Plan/Job, if the above Web Repository URL points to multiple repositories. | |
Mercurial Web Repository | Choose between using the BitBucket Web Repository Scheme (if you use BitBucket) or Mercurial's own default web server Default Web Repository Scheme (hgserve). | ||
FishEye | FishEye URL — The URL of your FishEye repository (e.g. ' Repository Name — The name of your FishEye repository (e.g. ' Repository Path — The path for your FishEye repository (e.g. '
| ||
Build Strategy | Choose one of the build strategy options (listed below), which will be used for triggering the execution of this Plan. You can change the Build Strategy at a later point in time as required. |
Screenshot above: Source Repository — CVS
Notes
Related Topics
Specifying the Source Repository for a Plan
Specifying the Source Repository for a Job
Attachments:



