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.