Moving from svn to git?

Folks,

Okay, so now that we’ve actually launched the next-generation version of our systems architecture and we’re starting to breathe again, one of the things we’re looking at is moving away from svn and putting everything on git.

We’ve already got a company github account (in addition to my own), and we have a minimal baseline familiarity with it, but I was wondering if anyone had any tips or tricks, or warnings about pitfalls, etc… that we should be familiar with?

From what I’ve heard, I believe we’re planning on using git-svn and svn2git to get at least most of our commit history, etc…, but if there are any better tools that we should know about, please speak up. And if you’ve got any pointers regarding Best Practices with git, especially as that applies to Chef, I’d love to hear about them.

Thanks!


Brad Knowles bknowles@ihiji.com
SAGE Level IV, Chef Level 0.0.1

Hi,

We haven't worked out a good process yet for tagging and managing promotion
of cookbooks and configuration through environments so I would be
interested in hearing about that from anyone who has a good story.

However we have been very happy with using braid (
GitHub - cristibalan/braid: Simple tool to help track vendor branches in a Git repository. ) as a way to
vendor in external repositories or even as a mechanism of sharing cookbooks
between projects. I highly recommend it.

On Sat, Feb 11, 2012 at 10:41 AM, Brad Knowles bknowles@ihiji.com wrote:

Folks,

Okay, so now that we've actually launched the next-generation version of
our systems architecture and we're starting to breathe again, one of the
things we're looking at is moving away from svn and putting everything on
git.

We've already got a company github account (in addition to my own), and we
have a minimal baseline familiarity with it, but I was wondering if anyone
had any tips or tricks, or warnings about pitfalls, etc... that we should
be familiar with?

From what I've heard, I believe we're planning on using git-svn and
svn2git to get at least most of our commit history, etc..., but if there
are any better tools that we should know about, please speak up. And if
you've got any pointers regarding Best Practices with git, especially as
that applies to Chef, I'd love to hear about them.

Thanks!

--
Brad Knowles bknowles@ihiji.com
SAGE Level IV, Chef Level 0.0.1

--
Cheers,

Peter Donald

Hi!

The basic steps how Etsy moved from svn to git last year are pretty well
documented at

http://codeascraft.etsy.com/2011/12/02/moving-from-svn-to-git-in-1000-easy-steps/
http://blog.johngoulah.com/2009/11/migrating-svn-to-git/

Beware that there was no heavy use of branching and tags in svn, so that wasn't
that much of a problem.

Cheers,
Daniel

On Tue, Feb 14, 2012 at 08:55:57AM +1100, Peter Donald wrote:

Hi,

We haven't worked out a good process yet for tagging and managing promotion
of cookbooks and configuration through environments so I would be
interested in hearing about that from anyone who has a good story.

However we have been very happy with using braid (
GitHub - cristibalan/braid: Simple tool to help track vendor branches in a Git repository. ) as a way to
vendor in external repositories or even as a mechanism of sharing cookbooks
between projects. I highly recommend it.

On Sat, Feb 11, 2012 at 10:41 AM, Brad Knowles bknowles@ihiji.com wrote:

Folks,

Okay, so now that we've actually launched the next-generation version of
our systems architecture and we're starting to breathe again, one of the
things we're looking at is moving away from svn and putting everything on
git.

We've already got a company github account (in addition to my own), and we
have a minimal baseline familiarity with it, but I was wondering if anyone
had any tips or tricks, or warnings about pitfalls, etc... that we should
be familiar with?

From what I've heard, I believe we're planning on using git-svn and
svn2git to get at least most of our commit history, etc..., but if there
are any better tools that we should know about, please speak up. And if
you've got any pointers regarding Best Practices with git, especially as
that applies to Chef, I'd love to hear about them.

Thanks!

--
Brad Knowles bknowles@ihiji.com
SAGE Level IV, Chef Level 0.0.1

--
Cheers,

Peter Donald