I have a large repository with multiple applications in it.
I am using a build tool to automatically retrieve and build the applications each morning.
The build tool uses the same Vault ID to retrieve and update the repository.
The concern/question I have is that when these [b]parallel[/b] builds are running they may conflict with each other when setting the working folder.
In other words, "last one in wins", when it comes to setting the working folder for a given repository path for a single vault ID.
Am I correct in the way this work?
Thanks,
Ed
Same Vault ID parallel builds
Moderator: SourceGear
If by Vault ID you mean the user name, then yes, if one process sets the working folder and another sets it again, the last one to set the working folder will be the way it stays.
However, if you doing a full get to a new folder everytime, you probably don't want to use a working folder Get, but a Get to a non-working folder instead. Then you wouldn't have to change the working folder at all.
However, if you doing a full get to a new folder everytime, you probably don't want to use a working folder Get, but a Get to a non-working folder instead. Then you wouldn't have to change the working folder at all.