1.7.1 CVS

If you are creating a new plan, start at step 5.

1. Click 'Home' to go to the Dashboard.
2. Click the 'All Plans' tab.
   
3. Locate the plan in the list and click this icon:
4. The 'Configuration' tab will be displayed. Click the 'Source Repository' sub-tab.
5. The 'Source Repository' sub-tab will be displayed (see screenshot below). Complete the fields as follows:

• 'Repository' — select 'CVS'.
• 'CVS Root' — Type the full path to your CVS repository root (e.g. ':pserver:me@cvs.atlassian.com:/cvsroot/atlassian'). Bamboo supports pserver, ext (ssh) and local repository access methods. Note that you can use global variables in this field (see 2.1.1 Using Variables).
• 'Authentication Type' — Select either 'Password' or 'SSH'. 
  • If you select 'Password', the following fields will appear:
    • 'Password' — (Optional) Type the password for your CVS repository.
    • 'Change Password' — (Will only appear after you have saved the plan) Select this check-box if you want to change the password that is used to access the CVS repository.
  • If you select 'SSH', the following fields will appear:
    • 'Private Key' — Type the absolute path of your SSH private key.
    • 'Passphrase' — Type the passphrase for your SSH private key.
    • 'Change Passphrase' — (Will only appear after you have saved the plan) Select this check-box if you want to change the password for 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.
• 'Module' — Type the name of the CVS module that contains the source-code.
  Currently Bamboo has limited support for CVS ampersand modules. To use an ampersand module, you will need to define a regular module with the same name as the ampersand module (since Bamboo expects there to be a directory with the specified checkout module name). For example:
  1. Create a module (e.g. allbuilds).
  2. Define an ampersand module with the same name. (The ampersand module can be empty.)
  3. In the 'Module' field, enter the following: allbuilds allbuilds &project2 &project2 &project3
• 'Version of Module' — Select either 'HEAD' or 'Branch/Tag'. If you select 'Branch/Tag', the following field will appear:
  • 'Branch name' — Type the relevant branch name or tag. Note that you can use global variables in this field (see 2.1.1 Using Variables).
    • 'Web Repository URL' --- (Optional) You can specify the URL of the plan's browsable repository. If you specify a Web Repository URL, then links to relevant files will be displayed in the 'Code Changes' section of a build result.
    • 'Include/Exclude Files' — (Optional) You can specify a particular inclusion or exclusion pattern for file changes to be detected.
    • 'File Pattern' — (Optional) The regular expression for file changes which you wish to include/exclude.
    • 'Web Repository Module' — (Optional) The plan's repository name, if the above Web Repository URL points to multiple repositories.
    • 'Build Strategy' — The default value, 'Poll the repository for changes', is a convenient option that requires no additional configuration. A number of other options are available; for details, please see 03. Triggering a Build. You can change the Build Strategy over time as required. The rest of the fields on this tab will vary depending on which Build Strategy you select.
    • Click the 'Save' button if you are editing an existing plan; or if you are creating a new plan, click the 'Next' button and go to 2.1 Specifying a Plan's Build Resources.