For each plan, you need to specify what type of source-code repository the plan will use, where the repository is located, and what type of build strategy the plan will use.
To specify a Subversion repository,
|
If you are creating a new plan, start at step 5.
- Click 'Home' to go to the Dashboard.
- Click the 'All Plans' tab.
- Locate the plan in the list and click this icon:

- The 'Configuration' tab will be displayed. Click the 'Source Repository' sub-tab.
- The 'Source Repository' sub-tab will be displayed. Complete the fields as follows:
Subversion Configuration
- 'Repository' — select 'Subversion'.
- 'Repository URL' — The location of your Subversion repository (e.g. http://svn.collab.net/repos/svn/trunk). Note that you can use global variables in this field (see Using Global or Build-specific Variables).
- 'Username' — (Optional) The Subversion username (if any) required to access the repository.
- 'Authentication Type' — Select either 'Password' or 'SSH'.
- If you select 'Password', the following fields will appear:
- 'Password' — (Optional) Type the password required by the Subversion username (if applicable).
- '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 Subversion 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.'
If you are planning to use remote agents the ssh private key file has to be copied to the agent box into the same location as specified.
- If you select 'SSL Client Certificate', the following fields will appear:
- 'Private Key' — Type the absolute path of your SSL client certificate.
- 'Passphrase' — Type the passphrase for your SSL client certificate.
Please note, the client certificate has to be in PKCS12 format and the client certificate file must be passphrase protected, otherwise a runtime exception is thrown by JDK security engine while opening the user key.
Advanced Options
(The following fields will only display if you select the 'Enable Advanced Options' check-box.)
- 'Enable Quiet Period:' — Select this setting to set Quiet Period parameters for the build plan.
- 'Quiet Period:' — This field will only display if 'Enable Quiet Period:' has been selected. 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.
- 'Maximum Retries:' — This field will only display if 'Enable Quiet Period:' has been selected. You can specify how many times Bamboo should check for new changes using the Quiet Period parameter before initiating a build. For example, if you have set the 'Quiet Period' to '10' seconds then Bamboo will check if a checkout has occurred in the last 10 seconds. If you have then specified 'Maximum Retries:' as '5', then Bamboo will perform this check five times before initiating the build, regardless of any activity during the Quiet Period of the last check.
- 'Detect Changes in Externals:' — (Optional) Select this check-box if your Subversion repository uses svn:externalsto link to other repositories (note that your externals must be in the root of the checkout directory, not in a subdirectory). Please note that you only need to select this check box if you require Bamboo to detect changes in the externals. If your externals references a particular (static) revision, you do not need to check this box.

If you use pre-1.5 Subversion client to access code checked out by Bamboo, you may encounter problems with your builds. This is due to the SVNKit upgrade in Bamboo 2.1.4. Please read this knowledge base article for further details. |
|
Screenshot: 'Source Repository --- SVN'
