Does anyone know the exact behavior of the vcs checkout rules for perforce? The reason I ask is I am trying to make use to build templates and have other branches just override the branch property set in the checkout rules and I'm having issues.
This is my example:
VCS Client mapping
VCS Checkout Rules
Under the branches path in perforce there are several branches there and I only want to sync the branchA which I would like to override with a property. My concern is that even though I state the checkout rule to only sync BranchA to the agent does it sync all of //depot/branches/... to the server before filtering out what to sync to the agent? If this is the case, having the server sync all of those branches everytime is pretty costly and this approach won't suit my needs which is why I need clarification. If this is not the case what am I doing wrong and how can I get only branchA to sync to the server and the agent by setting the checkout rules and to further my example other builds will be using this template and will be syncing branchB, etc.
Also why can't I use +://depot/branches/branchA in the checkout rules? Does it have to match what is after //team-city-agent/ in the vcs client mapping?