Subversion

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. Complete the fields as follows:
6. 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', 'SSH' or 'SSL Client Certificate'.
     • 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.
7. 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:externals to 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.
8. 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.
9. 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