We've recently renamed some branches. "Prod" got renamed to "G.12", and "QA" got renamed to "Prod". Now when the CI script attempts to set the working folder for "Prod" to the workspace path we use for production builds, it complains that another repository path is already set to that same path:
Code: Select all
[workspace] $ C:\Progra~2\SourceGear\VaultC~1\vault.exe SETWORKINGFOLDER -host vault.creditinfonet.com -username XXXXXXXX -password YYYYYYYY -repository ZZZZZZZZ -forcesubfolderstoinherit $/Gatwick/branches/Prod "C:\.hudson\jobs\Prod\workspace"
Exit code: -1
Exit code -1 unsuccessful; throwing IOException: <vault>
<error>
<exception>VaultClientOperationsLib.WorkingFolderConflictException: The following repository path is already assigned to this working folder: $/branches/G.12
at VaultClientIntegrationLib.ServerOperations.SetWorkingFolder(String repositoryFolderPath, String diskPath, Boolean createDiskPath, Boolean forceSubfoldersToInherit)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)</exception>
</error>
<result>
<success>False</success>
</result>
</vault>
- vault.exe UNSEWORKINGFOLDER as user XXXXXXXX
- runas /user:XXXXXXXX vault.exe UNSETWORKINGFOLDER
- Run VaultGUIClient.exe, log in as XXXXXXXX, unset working folder
- Run VaultGUIClient.exe, log in as XXXXXXXX, set working folder to another path
- runas /user:XXXXXXXX VaultGUIClient.exe, log in as XXXXXXXX, unset working folder
- runas /user:XXXXXXXX VaultGUIClient.exe, log in as XXXXXXXX, set working folder to another path