No working folder set error

[arunnagendran]

Hi, I was using the "robe070/vault2git2"July 2013 drop code. following exception we get as error while execute the Vault2Git.exe. Please help me in this regards.

here is config information: add key="Convertor.Paths" value="$/~master;$//Branches/~branch"/>

Error: Exception $/ has no working folder set. getting Version 8 from Vault repo. Waiting 5 secs and retrying...

Unhandled Exception: System.Exception: Cannot get transaction details for 217286

at Vault2Git.Lib.Processor.Pull(IEnumerable`1 git2vaultRepoPath, Int64 limitC ount) in C:\project\tool\vault2git_app\new\vault2git2-b713dcd09fedf83e61f9431536 47b09c4fd9a470\Vault2GitLib\Processor.cs:line 345 at Vault2Git.CLI.Program.Main(String[] args) in C:\project\tool\vault2git_app \new\vault2git2-b713dcd09fedf83e61f943153647b09c4fd9a470\Vault2GitCLI\Program.cs :line 217

[robe070]

I presume you are using branch master. Try improve-vault-performance . Its been running every night for 2 years and hasn't missed a beat.

[robe070]

I've not looked at the code in 2 years and I don't have time right now to decipher your issue.

Have you had this working at all? Whats your history with the tool?

Please provide entire config and the entire output from the tool.

I have not used the root folder previously - $/ It may not be supported. Or you may need to go back to the original repo. Just try and do one branch folder for now.

Here is my configuration: <?xml version="1.0" encoding="utf-8" ?>

[robe070]

I'll try that file again:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <appSettings>
    <add key="Vault.Server" value="devsrv"/>
    <add key="Vault.User" value="user"/>
    <add key="Vault.Password" value="password"/>
    <add key="Vault.Repo" value="lansa"/>
    <add key="Git.DomainName" value="lansa.com.au"/>
    <add key="Convertor.WorkingFolder" value="."/>
    <add key="Convertor.GitCmd" value="C:\Program Files (x86)\Git\cmd\git.exe"/>
    <add key="Convertor.Paths" value="$/vl/Trunk~trunk"/>
  </appSettings>
</configuration>

[arunnagendran]

Hi Robe, Thanks for your configuration data. Still we are seeing that issue: Actually what happen was migration start with version 1 and went up to 7. it got broken during version 8 migration and throw the exception. PS: I use " improve-vault-performance" drop . Below is the error message: C:\project\tool\vault2git_app\new\vault2git2-b713dcd09fedf83e61f943153647b09c4fd 9a470\Vault2GitCLI\bin\Debug>Vault2Git.exe Vault2Git -- converting history from Vault repositories to Git Using config file C:\project\tool\vault2git_app\new\vault2git2-b713dcd09fedf83e6 1f943153647b09c4fd9a470\Vault2GitCLI\bin\Debug\Vault2Git.exe.config use Vault2Git --help to get additional info Exception $/XXXXX_Repo has no working folder set. getting Version 8 from Vault repo. Waiting 5 secs and retrying...

Unhandled Exception: System.Exception: Cannot get transaction details for 217286

at Vault2Git.Lib.Processor.Pull(IEnumerable`1 git2vaultRepoPath, Int64 limitC ount) in C:\project\tool\vault2git_app\new\vault2git2-b713dcd09fedf83e61f9431536 47b09c4fd9a470\Vault2GitLib\Processor.cs:line 345 at Vault2Git.CLI.Program.Main(String[] args) in C:\project\tool\vault2git_app \new\vault2git2-b713dcd09fedf83e61f943153647b09c4fd9a470\Vault2GitCLI\Program.cs :line 217

[robe070]

Firstly, you've omitted to send your configuration file.

You have very long paths. I suspect that version 8 introduces a new directory level and that blows the length.

Move the gitrepo to c:\xxxx_repo and see if that makes a difference

[arunnagendran]

My bad, here is the configuration information. I found the reason for that error, The vault allow you to rename the repo directory name at any time. It means when you do the migration with latest repo directory name we get this error where older version keep the old repo name. Is it possible to skip the particular version from the migration process using this tool? or Is it possible to clone the label/tag independently without going over the version migration?

[robe070]

The last version number is part of the change set comment. If version 8 has the error, the last comment should contain 7. Change it to 8

Warm regards

Rob Goodridge

On 13 Aug 2015, at 12:37 am, arunnagendran notifications@github.com wrote:

My bad, here is the configuration information. I found the reason for that error, The vault allow you to rename the repo directory name at any time. It means when you do the migration with latest repo directory name we get this error where older version keep the old repo name. Is it possible to skip the particular version from the migration process using this tool? or Is it possible to clone the label/tag independently without going over the version migration?

— Reply to this email directly or view it on GitHub.