Git-Tf clone --deep is very slow for large repository & How to prevent automatic linking of commit to existing WIT.

[vidya...@tieto.com]

Git-Tf clone --deep is very slow for large repository. Do you know any way to get faster clone for large repo with all history.

We tried small repo tfvc to git migration using git tfs clone command, but we face issue that all commits of migrated code get linked with existing WIT . and then we have to do some manual work to remove that commit linking from WIT.

Do you know how to prevent that in next migration?

Thanks in Advance.

[Philippe Miossec]

Sorry, this is not the support forum of the 'git-tf' tool (that is deprecated by Mircrosoft, so I think that there is no way to get support :( ).

So we can't help you on that.

This is the support forum for the 'git-tfs' tool ( https://github.com/git-tfs/git-tfs/ ) that the same thing. More info on that here: https://stackoverflow.com/a/12867309/717372

To give you some hint, git-tf is known to be slow where 'git-tfs' is a little quicker (but I don't know how much) but you should know that the biggest problem come from that TFVC is very slow/inefficient in the way it transfer data.

So everything you will try will be quite slow (even a migration with git-tfs).

Good luck!

--
You received this message because you are subscribed to the Google Groups "git-tfs-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to git-tfs-dev...@googlegroups.com.
To post to this group, send email to git-t...@googlegroups.com.
Visit this group at https://groups.google.com/group/git-tfs-dev.
For more options, visit https://groups.google.com/d/optout.

[Nikam Vidya]

Hi,

 

We have migrated our source code using git tfs as well.

We tried small repo tfvc to git migration using git tfs clone command, but we face issue that all commits of migrated code get linked with existing WIT . and then we have to do some manual work to remove that commit linking from WIT.

Do you know how to prevent that in next migration?

 

 

Thanks,

Vidya.,

--
You received this message because you are subscribed to a topic in the Google Groups "git-tfs-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/git-tfs-dev/M7JOnGYPuE4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to git-tfs-dev...@googlegroups.com.

[Matt Burke]

Hi Vidya,

When you say that the commits are linked to work items, do you mean that there's a "Workitems:" line in your commit message? If so, that's not added by default, so you probably have the "export-metadatas" config option set, or you provided the "--export" option to "git-tfs clone". 

Read more about git-tfs's config: https://github.com/git-tfs/git-tfs/blob/master/doc/config.md

Read more about clone's options: https://github.com/git-tfs/git-tfs/blob/master/doc/commands/clone.md 

--
Matt

[Nikam Vidya]

Hi,

 

It is not adding workitems in the commit message .

And we are using simple “git Tfs clone “tfs url till collection name” $/Project name/trunk”

and

It added/ linking any changeset/ commit to existing work item template (eg. like task/ user story) of destination project where we have migrated our source code.

 

Thanks and regards,

Vidya.

[Nikam Vidya]

Hi again,

 

Correction: Yes, it is adding work items id in the commit message as well as It added/ linking any changeset/ commit to existing work item template (eg. like task/ user story) of destination project where we have migrated our source code.

Thanks,

[Matt Burke]

Hi Vidya,

I'm not sure what you mean by "It added/ linking any changeset/ commit to existing work item template (eg. like task/ user story) of destination project." I haven't used TFS in years, so I'm probably just not up to date on what TFS does when you push a Git repository to it.

As for the work item IDs in commit messages, I'm pretty sure those come from here (https://github.com/git-tfs/git-tfs/blob/d9628cda0a80235c1e9707d246eb2412da780509/src/GitTfs/Core/GitTfsRemote.cs#L488-L497). That's controlled by the options I mentioned in my last message. Can you maybe share an example of a commit message that git-tfs is creating, and how you'd like it to be different?

--

Matt