I have a requirement to mirror the data from a Vault repository into an existing VSS repo on a regular basis (probably not on every checkin, more like once every 24 hours).
Has anyone had a go at doing this and if so how did they accomplish a reliable and working process?
I know this is a bit of an odd request however the logic is that we wish to develop using Vault but deliver a VSS hosted version of the source to an external party on a daily basis (their company std source code repo is vss).
Thanks in advance,
j3r3m7
Mirror repository in VSS
Moderator: SourceGear
One way you could do this is with Shadow Folders. A shadow folder is a local folder that contains the contents of a repository folder, and is kept up-to-date in the shadow folder by the Vault server as changes are applied to repository folder.
Once the Shadow Folder is created, you could then use the VSS command line client (ss.exe) in an automated script to do a get from the Shadow Folder to the VSS database.
If the VSS database is remote, you could conside using our sibling software, SourceOffSite for remote access to the VSS database. SOS also has a command line client.
For Shadow Folder information, see Vault Admin Help->Repository Options->Configure Shadow Folders.
Once the Shadow Folder is created, you could then use the VSS command line client (ss.exe) in an automated script to do a get from the Shadow Folder to the VSS database.
If the VSS database is remote, you could conside using our sibling software, SourceOffSite for remote access to the VSS database. SOS also has a command line client.
For Shadow Folder information, see Vault Admin Help->Repository Options->Configure Shadow Folders.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Linda,
Thanks for your quick reply One thing I guess that adds complication is that the Vault server is external to the VSS server network so what might be an option is to use CruiseControl.net to pull in the latest Vault code, then push it into VSS.
What would be the gold plated solution would be to retain the history that builds up in Vault in the VSS mirror. I'll have a play and report back if I get a slick solution. I'm sure with cc.net and nant on my side we'll be ok.
On a side note are there any 'Best Practice' web articles for distributed team source control using Vault, I'd be interested in practical examples of team setups etc..?
Regards,
j3r3m7
Thanks for your quick reply One thing I guess that adds complication is that the Vault server is external to the VSS server network so what might be an option is to use CruiseControl.net to pull in the latest Vault code, then push it into VSS.
What would be the gold plated solution would be to retain the history that builds up in Vault in the VSS mirror. I'll have a play and report back if I get a slick solution. I'm sure with cc.net and nant on my side we'll be ok.
On a side note are there any 'Best Practice' web articles for distributed team source control using Vault, I'd be interested in practical examples of team setups etc..?
Regards,
j3r3m7
Here's a link to get you started.
http://www.ericsink.com/scm/scm_intro.html
If you have specific questions, let us know.
http://www.ericsink.com/scm/scm_intro.html
If you have specific questions, let us know.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager