1.7.3 Perforce

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:

• 'Repository' — select 'Perforce'.
• 'Perforce P4 client' — The location (on the Bamboo server) of the Perforce P4 client application. On UNIX systems this is typically /usr/local/bin/p4.
• 'Port' — Type either the port to which the Perforce client will connect, or the Perforce server itself. This is the Perforce P4PORT environment variable that tells Bamboo which p4d (Perforce server) to use.
• 'Client' — The name of the Perforce Client Workspace which Bamboo will use. The Client Workspace determines which portions of the depot are visible in your Workspace Tree and where local copies of depot files are stored in your workspace.
   If you wish to have several plans pointing to the same Perforce depot, you will need to set up a different client for each.
• 'Depot' — The client view of the depot that contains the source-code files for this plan. This is typically in the form //<clientname>/<workspace_mapping>/... For details please see the Perforce User's Guide.
  To build to a particular Perforce label, enter the following: //Repo/Project/dev/...@mylabel (where 'mylabel' is the label you wish to match). 
• 'Username' — (Optional) The Perforce username that Bamboo will use when it accesses the server ('Port'). Leave this field blank if you want Bamboo to use the default Perforce user (i.e. the OS username).
• 'Password' — (Optional) Type the password required by the Perforce 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 Perforce repository.
• 'Web Repository URL' — (Optional) You can specify the URL of the plan's browsable repository. 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 URL' --- (Optional) You can specify the URL of the plan's browsable repository. If you specify a Web Repository URL, then links to relevant files will be displayed in the 'Code Changes' section of a build result.
• '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 Module' — (Optional) The plan's repository name, if the above Web Repository URL points to multiple repositories.
• '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 03. 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.
• Click the 'Save' button if you are editing an existing plan; or if you are creating a new plan, click the 'Next' button and go to 2.1 Specifying a Plan's Build Resources.