Shadow Folder Issue

[TalismanUser]

We currently have a number of applications stored in our Vault repository and are looking to implement Shadow Folders in order to deploy changes. After some testing we’ve found that (for larger applications at least) the process fails.

After ensuring that the content of the repository is consistent with the files on the server we defined the Shadow Folder to point at the same location. We then imported a file into the repository and waited for the change to be applied to the Shadow Folder. After over half and hour of waiting, the Shadow Folder still failed to update.

Running the same test with an initially empty Shadow Folder works fine with all changes being applied as expected.

The problem is that due to the importance/usage of the applications, we don’t want to have to empty the Shadow Folder and thus take them offline. Is there any way in which we can define the Shadow Folder which is already populated with the required files?

We are using Vault 3.1.9 and wondered if perhaps this was a know issue? Would upgrading to a newer version mean that we could avoid having to empty the desired Shadow Folder?

[Beth]

The behavior you have observed is how Shadow Folders work. They need an empty folder to populate with the latest code and would continue keeping the folder updated from there.

[jeremy_sg]

There is now a Deploy Power Toy, which can be downloaded at: http://sourcegear.com/vault/vaultpowertoys.html