Upgrade from 3.5.(1?) to 4.0.5 / Command Line / FinalBuilder

tafountain · Post by **tafountain** » Wed Dec 05, 2007 11:32 am

We just upgraded our Vault server and all clients to the latest - 4.0.5. We have automated build and deployment scripts on both sides of our house - .NET and Delphi. The .NET guys use CCNet and NANT to do their build and deployments - and it all works fine. The Delphi guys use a product called FinalBuilder (version 4.2.0.305) to do their build and deploys. We seem to be having an issue with the FinalBuilder side where it generates the following command:

Code: Select all

get -user "<somename>" -password "<somepassword>" -host "<someserver>:<someport>" -repository "<repository name>" -destpath "<fully qualified path down several levels deep>" -makereadonly "$/<some vault location where the files reside>"

This causes the error

Code: Select all

  <error>
    <exception>System.Exception: You have supplied a destPath which matches the working folder already associated with this object.  Remove the destpath argument when updating a local working folder, or remove the working folder association for <some vault location where the files reside>
   at VaultClientIntegrationLib.GetOperations.ProcessCommandGetToLocationOutsideWorkingFolder(String[] objectPaths, GetO
ptions getOptions, String destPath)
   at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
   at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)</exception>
  </error>

This obviously seems like a change in the product. Can you identify if there is a workaround for this?

lbauer · Post by **lbauer** » Wed Dec 05, 2007 11:41 am

Does the user running this command already have a working folder set to the same location as you're using for -destpath? -destpath is used to get files to a non-working folder.

tafountain · Post by **tafountain** » Wed Dec 05, 2007 11:46 am

Yes, the dest path is the same as the working folder. But it's always been that way (for 1+ years). It wasn't until the upgrade from 3.5.? to 4.0.5 we started having an issue.

lbauer · Post by **lbauer** » Wed Dec 05, 2007 4:22 pm

There have been some changes to the command line client, and -destpath has been deprecated. I believe it still works if you do a get to a non-working folder.

Since you are doing a Get to a working folder, you don't need -destpath. The CLC assumes the working folder.

If you are getting to a non-working folder, you can use -nonworking folder instead of -destpath.

tafountain · Post by **tafountain** » Thu Dec 06, 2007 8:14 am

Linda, the only issue there is the FinalBuilder product generates the command line options and we have no direct control over it. Is there anyway to workaround this issue?

Also, can you identify the version that this feature changed?

lbauer · Post by **lbauer** » Thu Dec 06, 2007 9:11 pm

You can use -destpath if you unset the working folder. The -destpath option still works, but we've added -nonworking folder in Vault 4.0.