Is there a way to map multiple branches of a project to the same working folder? I have some engineers that said this used to be possible in our previous version of Vault (3.1.8 which we just upgraded from), but it seems to have been removed in the current version.
This is a burdensome issue for our engineers as many of them develop for Integrated Circuits and have to define path locations and such in a static way in the code, so when they are forced to map different branches to different physical paths, it breaks their code.
How can this be accomplished? If it has been disabled, can we please get it back in a 6.0.2 patch? We desperately need this functionality. Thanks.
Mapping Multiple Branches to the Same Working Folder
Moderator: SourceGear
Mapping Multiple Branches to the Same Working Folder
Last edited by Chiramisu on Thu Jan 15, 2015 10:44 am, edited 1 time in total.
Re: Mapping Multiple Branches to the Same Working Folder
The original intent of Vault was to have one working folder per repository folder. However, there was a bug in earlier versions that allowed this.
Having multiple repository folders map to the same working folder caused inconsistent file status for users and sometimes caused files to be overwritten.
We changed this behavior in Vault 3.5.3. Sorry it caught you by surprise when you upgraded. We don't have plans to go back to allowing multiple repository folders to use the same working folder.
One way some users still do this is by having projects in different repositories. Then they can use the same working folder for more than one project, as long as they are in different repositories.
Having multiple repository folders map to the same working folder caused inconsistent file status for users and sometimes caused files to be overwritten.
We changed this behavior in Vault 3.5.3. Sorry it caught you by surprise when you upgraded. We don't have plans to go back to allowing multiple repository folders to use the same working folder.
One way some users still do this is by having projects in different repositories. Then they can use the same working folder for more than one project, as long as they are in different repositories.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Re: Mapping Multiple Branches to the Same Working Folder
Yikes! That's a darn shame. Sure not going to make our engineers happy with that one. Are there any other workarounds? We already have plenty of repositories and I'm trying to keep things simple.
As for the concerns with regard to overwriting code, that's PRECISELY what is desired by our product engineers. They require the ability to be able to swap between different branches for testing purposes. Is there any chance of making this an OPTION with a WARNING in the next patch? Not being able to do this creates somewhat of a headache for our engineers and hampers their productivity.
As for the concerns with regard to overwriting code, that's PRECISELY what is desired by our product engineers. They require the ability to be able to swap between different branches for testing purposes. Is there any chance of making this an OPTION with a WARNING in the next patch? Not being able to do this creates somewhat of a headache for our engineers and hampers their productivity.
Re: Mapping Multiple Branches to the Same Working Folder
We're sorry this has caused an inconvenience for your developers. Perhaps if we had a better understanding of your work flow and what your developers are trying to accomplish by mapping two repositories to one working folder, we might have some suggestions for a workaround.
Email me at support at sourcegear.com, ATTN: Linda.
Please include a link to this forum post.
Email me at support at sourcegear.com, ATTN: Linda.
Please include a link to this forum post.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager