Hello Beth...
In this particular Repo, we essentially have EVERYTHING under "$/MainLine".
All Shares are within this folder, none extend out of it.
A Branch is essentially a Product Version eg: "$/ProducName_##.##.##.##".
We generally build out of mainline.
We apply code patches to Product Branch and build out of it if patches need to be distributed to our customers.
Shares must be maintained in Mainline and within all Branches and are relative only within the Branch/Mainline that they exist in.
Any Idea why I get the error indicated in the first post?... Branching smaller sub-Folders has worked in the past.
Also, is there an upper limit to how many files, or size, of a folder that is to be branched?... In our implementation, 50GB and/or 100,000+ files, wouldn't be unexpected. Our "Vault" Server Database is in excess of 80GB, with about 25 Repositories. Most are relatively small. This particular one is probably 50 GB, by itself, and there is another of about 20GB, or some ratio that results in about 80GB...
Not that it has any bearing on the issue, but we use CCNet as our Build Engine. I also don't use your CLI, but rather a DotNet API Shell around your Vault Library Dll's (Don't Ask
).
An example of usage:
BuildServer 1 Working Folder is derived from "$/Mainline".
BuildServer 2 Working Folder is derived from "$/ProductName_##.##.##.## Branch".
Suggestion: It would be cool if you could Branch "$", but that might complicate things
.
FYI: I would like to break these repositories up over 2 or 3 Servers, but your cost (and the cost of the additional Server Os's) is prohibitive.
)