This documentation relates to an earlier version of Bamboo.
View

Unknown macro: {spacejump}

or visit the current documentation home.

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. :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, Plan or Build-specific Variables).

(info) If you are importing a Maven 2 Project, this location should contain your project's pom.xml file.

Authentication TypePasswordChoose 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
Passphrase — The passphrase 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. 

 (Only available when configuring an existing Plan) 

Module

Type the name of the CVS module that contains the source-code.

(info) 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

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.

(info) Note that you can use global variables in this field (see Using Global, Plan or Build-specific Variables).


Common Repository Configuration

Force Clean BuildYou 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 buildYou 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 FilesYou 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 RepositoryChoose 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. '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/').

How do I determine my Repository Path?

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

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.

(warning) You may need to configure other options specific to your chosen build strategy.

(warning) If you select Manual & dependent builds only when creating a new Plan, an initial build will not automatically be run. You can force an initial build to be executed automatically by adding the fire.initial.build.for.manual.strategy to your bamboo.cfg.xml file as described in Configuring System Properties.



Screenshot above: Source Repository — CVS

Notes

Related Topics

Specifying the Source Repository for a Plan
Specifying the Source Repository for a Job

3 Comments

  1. PeTomasek

    Apr 08, 2010

    How does local CVSROOT look like? My repository is located in C:\var\cvsrepo, but none of the following works for me:

    • :local:\var\cvsrepo
    • :local:/var/cvsrepo
    • \var\cvsrepo
    • /var/cvsrepo

    However, running a CVS client in a command-line works fine:

    cvs -d /var/cvsrepo co foo

    I also have FishEye installed – how could I utilize FishEye instead of CVS access?

    1. Giles Gaskell

      Oct 05, 2010

      Hello Petr,

      Apologies for this very late response. I'm not sure if you had found a solution since posting your message, but if not, it looks like you have a CVS server installed on a Windows-based operating system. If so, you might want to check out this information - particularly if your Bamboo system is installed on a Linux- or UNIX-based operating system and needs to communicate with a Windows-based CVS server.

      Alternatively, if you are using CVSNT you could try specifying a CVS Repository Prefix, so that you do not have to specify a Windows drive letter in the Bamboo CVS Root field.

      Cheers,
      Giles.

  2. Anonymous

    Mar 02, 2011

    How can I turn up the debugging for CVS or use a local version of CVS.  The command it displays in the 'Running CVS command' for checkout is correct (ran on server as different account users) but I'm getting no data and no errors. 



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.