Git Import/Export
Moderator: SourceGear
Re: Git Import/Export
Sorry you are unhappy with SourceGear. As a software vendor, our priorities are to make Vault the best possible version control tool for our users. So we are devoting development time to new features, bug fixes, etc. for Vault 6.0.
As you have experienced yourself, writing an export or import tool that must interface with a different software is difficult and time consuming. If we spend development time on that, then it takes away time from making our product better for users that are staying with Vault.
Generally, if users are moving to another software, the other software company or its users take it upon themselves to write an export tool. For instance, tens of thousands of VSS users have been moving to Vault. It made sense for us to devote development time creating a VSS Import Tool. But because our development resources are not unlimited, it is unlikely we would devote them to an export tool to another software.
We certainly will provide information about using the Client API, if you have specific questions about its functionality. Any type of export would probably be slow because you are retrieving history in one database and and recreating it in another. Plus there are shares, branches, pins, labels, user associations, etc. It's not just a matter of getting files and putting them into another database.
As you have experienced yourself, writing an export or import tool that must interface with a different software is difficult and time consuming. If we spend development time on that, then it takes away time from making our product better for users that are staying with Vault.
Generally, if users are moving to another software, the other software company or its users take it upon themselves to write an export tool. For instance, tens of thousands of VSS users have been moving to Vault. It made sense for us to devote development time creating a VSS Import Tool. But because our development resources are not unlimited, it is unlikely we would devote them to an export tool to another software.
We certainly will provide information about using the Client API, if you have specific questions about its functionality. Any type of export would probably be slow because you are retrieving history in one database and and recreating it in another. Plus there are shares, branches, pins, labels, user associations, etc. It's not just a matter of getting files and putting them into another database.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Re: Git Import/Export
I understand.
Would you be able to give me a query that showed all files and its path and its versions and labels?
Would you be able to give me a query that showed all files and its path and its versions and labels?
Re: Git Import/Export
I have a query that might help.
Email support at sourcegear.com, Attn: Linda. Please include a link to this forum post.
Email support at sourcegear.com, Attn: Linda. Please include a link to this forum post.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Re: Git Import/Export
Linda,
Does the Folder Import/Export tool now have any option to leave out history? We are a bit behind 5.1.
It'd like to make a copy of a repository by using the tool on the root folder but that takes a really long time. For this purpose the current versions only are fine but I want to keep my complex web of share/branching.
Thanks,
Ian
Does the Folder Import/Export tool now have any option to leave out history? We are a bit behind 5.1.
It'd like to make a copy of a repository by using the tool on the root folder but that takes a really long time. For this purpose the current versions only are fine but I want to keep my complex web of share/branching.
Thanks,
Ian
Re: Git Import/Export
Folder Export Import still imports all history.
I've logged feature request 17506 to import only the "tip" version of a folder, but include shares, branches, etc.
I've logged feature request 17506 to import only the "tip" version of a folder, but include shares, branches, etc.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Re: Git Import/Export
Linda,
Did feature request 17506 ever get implemented? We really need it.
Thanks,
Ian
Did feature request 17506 ever get implemented? We really need it.
Thanks,
Ian
Re: Git Import/Export
This feature hasn't made it into the recently release.
EDIT: Sorry, I just realized you were talking about something else than what the initial forum thread covered. The feature you mentioned isn't implemented yet.
EDIT: Sorry, I just realized you were talking about something else than what the initial forum thread covered. The feature you mentioned isn't implemented yet.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
-
- Posts: 61
- Joined: Thu Nov 13, 2014 10:12 am
- Location: Lake in the Hills, IL
Re: Git Import/Export
Export PS1 script: https://stackoverflow.com/questions/107 ... -to-gitSee bottom comments. Worked for a single project so far - not able to get history although the XML it pulls back shows the history. Our plan is to take the latest updates and import to Git (in our case gitlab) while leaving the historical in Vault until we feel safe to discard the files.
Thanks!
Eric
Eric