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:
   
6. CVS configuration
   • '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 Using Global or Build-specific 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. Please note that this parameter is mandatory for CVS, as CVS allows partial checkouts.
   • '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 Using Global or Build-specific Variables).
       
7. Common Repository Configuration

   • 'Force Clean Build' (Optional) — You can force Bamboo to remove the source directory and check it out again prior to each build by selecting this option. Please note that this will greatly increase the time it takes to complete a build.
   • '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:' — Select the type of web repository ('None', 'Generic Web Repository', 'FishEye') to be associated with this build. You will be able to view code changes related to your build via the build results.
     • If 'Generic Web Repository' selected:
       • '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 plan's repository name, if the above Web Repository URL points to multiple repositories.
     • If 'FishEye' selected:
       • 'FishEye URL' — The URL of your FishEye repository (e.g. 'https://atlaseye.atlassian.com/').
       • 'Repository Name' — The name of your FishEye repository (e.g. 'Bamboo'). This is effectively the alias for your repository path.
       • 'Repository Path' — The path for your FishEye repository (e.g. '/atlassian/bamboo/').

         リポジトリのパスを特定する方法

         If you have previously run builds with changes from your repository, the easiest way of determining your repository path is to view the code changes and copy the path from the start of the path of one of the changed files, up to (but not including) the appropriate root directory. The root directories for repositories are the ones shown by FishEye when browsing a repository (e.g. trunk)). For example, if a code change listed /atlassian/bamboo/trunk/bamboo-acceptance-test/pom.xml, the path would be /atlassian/bamboo/.
         If you have not previously run builds with changes from your repository, you will need to ask your FishEye administrator for the repository path indexed by FishEye.

   • '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 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.
     If you select to trigger builds manually when creating a new plan, an initial build will not automatically run. You can change this to force an initial build to automatically run, even if manual triggering is selected, by adding the fire.initial.build.for.manual.strategy to your bamboo.cfg.xml file as described in Configuring System Properties.
8. Click the 'Save'/'Done' button if you are editing an existing plan. If you are creating a new plan, you can either click the 'Save'/'Done' button to create the plan without completing the rest of the wizard (check/uncheck the 'Enable Plan' checkbox to create your plan as enabled/disabled as desired) or click the 'Next' button to go to the next page:
   Specifying a Plan's Builder