[Bamboo Knowledge Base]
The instructions on this page describe how to configure Bamboo to use a Perforce source repository.
To add a new Perforce repository, navigate to the source repository settings for a plan or job, as described on Specifying the source repository.
|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 (Workspace) (3)
|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.
Do not create two Plans/Jobs that use the same client (e.g. one client set to manage, the other client set to not manage). This setup will create major issues in your builds.
|The client view of the depot that contains the source code files for this Plan/Job. This is typically in the form
//<clientname>/<workspace_mapping>/... For details please see the Perforce User's Guide.
Bamboo sets the client root to its working directory, which means that code will be checked out to the 'working directory/
|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).
|Type the password required by the Perforce username (if applicable).
|Let Bamboo manage your workspace (4)
|This field indicates whether or not you want Bamboo to manage your workspace.
|Use Client Mapping For Change Detection
|Select this option if you use overlay mappings for your workspace. Your workspace must be available on the Bamboo Server
|Enable Quiet Period
|Specifies a delay after a single commit is detected before the build is started. This allows multiple commits to be aggregated into a single build.
Allows you to specify the files that Bamboo should, or should not, use to detect changes.
|Enter a regular expression to match the commit messages for changesets that should not start a build.
If your repository can be viewed in a web browser, select the repository type.
This allows links to relevant files to be displayed in the 'Code Changes' section of a build result.
Generic Web Repository
FishEye – specify the URL and other details for the repository:
See Integrating Bamboo with FishEye for more information.
How do I determine my Repository Path?
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.
root). You need to ensure that you enter a Client Workspace in the 'Client' field that will be used solely for Bamboo.