Importing complex SVN into stash

Jeff Warnica

I'm trying to evaluate Stash, specifically with an end goal of migrating from a very legacy SVN setup as well. I'm new to this team, and was not involved in the inital SVN layout. Anyway, long story short, its a mess. I've used svn2git, and the rather generic Atlassian docs, but, well, GIGO, I suppose. I see that pull requests can go across repositories (and assume, automatic triggers could, too). Maybe I just need to build things out by hand.

I guess, I'm wondering if there is a more full "worst case" import scenario?

cofarrell

Hi Jeff,

I'm not quite sure what you're asking?

Just a few things:

1. Have you seen git filter-branch? It's pretty much the swiss army knife of repository manipulation, don't leave home without it. You could, for example, extract sub repos from your single SVN repo. Or even move folders (and history) from one place to another. And much more. Not sure if that's helpful?

2. I haven't used svn2git, generally git-svn is awesome except for speed. If you're history is missing something that's where I would start.

3. Not sure what you mean by PRs across repositories? We only allow users to create PRs across one repository and any child forks. By automatic triggers do you mean hooks? Hooks are generally enabled and configured per repository.

4. What do you mean full 'worst case' import scenario?

Apologies that I've not quite understood your question.

Charles