import from TFS

[bwhite]

We are doing a project with another team that is using TFS.
1) Because of the time difference we don't expect to be working on any files at the same time.
2) We are having numerous problems getting TFS to work correctly.
3) It is a pain to have to switch VCS in VS from one project to the other.

So we are thinking about a nightly import/export.

We would download the latest from TFS, import it into Vault at 7 AM.
Then, in the evening, we would get latest from Vault and submit the changes to TFS.

This all would happen in the background and to us it would look like any
other Vault project. The only downside I see is that we lose detail in
Vault about who made changes on their side and similarly they couldn't
see who made changes on our side. It would just show "Remote User" or
some such as having made the change. But we don't care about that.
Any other downsides?

Any tools for doing this automatically instead of our manual approach?

Lacking that, exactly how do we "import it into Vault" from a batch file?

Thanks,
Brad.

[lbauer]

Vault has a commandline client that you could use in a batch script. It's available in the Vault GUI client directory.

For documentation, see this:

http://download.sourcegear.com/misc/vau ... nt/clc.htm

Or, cd to the Vault Client directory and type vault help or vault helphtml (for html formatted help)

[sirkirby]

Its the command line still the only option for doing this type of migration? I'm thinking of bringing my team back to vault after being on tfs 2010 for over a year now and would like to preserver the code history if we can. We still have quite a bit of code in fortress 1.x as well, so our ultimate goal would be to bring it all under one roof with vault 5.

I've been a long time fan and user of vault since the pre v1 days (loved that single dev license) and while tfs looks good, especially if your an ms partner, the hidden cost of administration is a bit overwhelming. tfs, sharepoint, reporting service, etc. I really like the fact that you guys now support integration with OnTime too, which we also use...that will help us in the short term as we migrate off of axosoft as well.

Thanks,

Chris

[bwhite]

Sorry I can't give you an experience report.
We ended up suffering with TFS and not doing the transfer.
The project was finally canceled and put out of its misery.

Brad.

[lbauer]

bwhite's project was more complex becasue they were transferring from TFS to Vault and back on a regular basis.

Although we don't have a specific import from TFS, you could do a version by version GET from the root level of the TFS repository into a directory on disk and use that directory as the working folder for $/ (root) in Vault. First you would GET version 1 of your project from TFS and the ADD those files to Vault. Checkout the files in Vault to make them writable, and continue to GET from TFS and Checkin subsequent GETS of versions from TFS.

Vault also has a Client API with that could be used for the same purpose.