I am migrating from VSS to Vault and am trying to decide on exactly how to transfer my current projects over. Does anyone have any advice on how to break things down into Repositories?
In our environment we essentially have three development teams and a testing team. There is a little bit of overlap between the teams, but no overlap in the development projects or need to share files between the projects for the teams.
Should I be creating a repository per application, per team, or just one big repository? In the VSS world we had a single VSS DB per team. Is a repository pretty much analagous in Vault to a VSS DB? Are there any trade-offs to lumping things together into a single repository that I should be aware of?
Best practices for setting up repositories in Vault
Moderator: SourceGear
The place to start would be our KB article: Best practices for setting up repositories.
Data can't be shared between repositories easily, so items that need to share code back and forth with each other should be in the same repository.
Using multiple repositories can give you better performance rather than having one huge tree. You don't necessarily want 100's of repositories either as then that affects things in a different way.
Data can't be shared between repositories easily, so items that need to share code back and forth with each other should be in the same repository.
Using multiple repositories can give you better performance rather than having one huge tree. You don't necessarily want 100's of repositories either as then that affects things in a different way.