Multiple Repository Sync in Perforce
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
In Bamboo versions before 3.3 it is not possible to configure multiple depots in a single plan.
Solution
Workaround
Perforce has client workspaces which are the equivalent of sandboxes. Workspaces have multi line views which allow mapping from any part of the repository into your workspace.
Have multi-line views in your workspace. http://kb.perforce.com/UserTasks/ConfiguringP4/MappingMulti..Directories
As of server release 2004.2, lower lines that begin with a "+" ("overlay mappings") do not completely override earlier mappings in the previous fashion:
1
2
//depot/main/util/... //freds-client/util/...
+//depot/fred/util/... //freds-client/util/...Instead, overlay mappings override mappings on a file-by-file basis. For example, if any given file exists in //depot/fred/util, then it will be mapped to the corresponding location in //freds-client/util. However, if a file exists in //depot/main/util but not in //depot/fred/util, then that file will be mapped to //freds-client/util instead.
Was this helpful?