Documentation for Bamboo 4.0.x. Documentation for earlier versions of Bamboo is available too.

When you create a new plan, you specify the default source repository to be used for your plan builds. Bamboo checks out the code from the repository before performing all the subsequent tasks for the build.

Bamboo is able to connect to a variety of SCMs. For details, please refer to the following pages (and see Notes below):

If you are a Bamboo server administrator, you can configure a shared source repository. Shared repositories are available to all plans on the server.

Screenshot: Configuring a job — Subversion Source Repository

Viewing the source repository for a plan

To navigate to the source repository settings for a plan:

  1. Click Dashboard  and then the All Plans tab.
  2. Locate the plan in the list and click its icon. The plan's configuration pages will be displayed.
  3. Click the Source Repositories tab to see all the repositories configured for this plan.
  4. Click the name of a repository to see its particular settings (see screenshot below).

Screenshot: Viewing the details for a source repository of a plan

 

Viewing the source repository for a job

To navigate to the source repository settings for a job:

  1. Click Dashboard and then the All Plans tab.
  2. Locate the plan in the list which contains the job you wish to configure and click the plan's name. The plan's 'Plan Summary' page will be displayed.
  3. Choose Actions > Configure Plan.
  4. Click the name of the job in the 'Plan Navigator' on the left. The job's Summary will be displayed.
  5. Click the Tasks tab and then the Source Code Checkout task, to see the repository settings for your job. (Note that this may not be present in your job configuration if it has been explicitly removed by the user.)

For a description of configuring the Source Code Checkout task see Checking out code.

Notes

7 Comments

  1. Anonymous

    For others using fisheye as your 'Web Repository':

    I've had good experience using http://my/atlassian.local/fisheye/browse as my web repository url

    (fisheye is visible @ http://atlassian.local/fisheye/ in our setup)

  2. PeTomasek

    I see only the following repository types:

    • CVS
    • Subversion
    • Perforce

    Why is Fisheye missing in the list? And why CVS setup requires password authentication for local repository?

  3. Giles Gaskell

    Please note that FishEye is not a type of source code repository. FishEye is a tool for accessing and interacting with source code housed in a Subversion, Git, Perforce, ClearCase, CVS or Mercurial source repository.

    The documentation on how to integrate FishEye with your Bamboo Plan/Job is explained on each source repository documentation page (i.e. child pages of this one).

    Finally, Bamboo does not require you to specify a password for source code repositories — the 'Password' field is optional.

    Cheers,
    Giles.

  4. Anonymous

    I am not sure why there is no description in documentation regarding build of particular label?

  5. Anonymous

    Is there a way to map multiple FishEye Repositories to a single Bamboo Plan?

    1. Anonymous

      I would also like to find out if there is a way to map multiple perforce branches to a single bamboo plan.

  6. Anonymous

    Anyone know why a Shared Repository wouldn't show up in a Plan's repositories (when I'm trying to create a project task for source code checkout) ?