• Article
  • May.28.2013

How we migrated our open-source add-ons to Bitbucket

  • May.28.2013
  • Reading time mins


We have 4 open source add-ons :

In the past few years, we used to host our open source add-ons on Atlassian Studio’s SVN repository. But in March 2013, Atlassian decided to shut the Studio platform down with the associated wikis, issue trackers as well as the source hosting with the dedicated SVN repository.

The solution was to migrate our products to Bitbucket, Atlassian’s DVCS hosting platform (Git or Mercurial) and here’s how we went about it.

Migration summary

This migration took place in several steps (SVN -> Git migration tutorial) :

  • Atlassian generated an SVN dump file of our 4 SVN projects before the platform was closed. A simple checkout would have been sufficient to retrieve the sources and send them to Bitbucket, but this extract allowed us to keep the commits metadata, such as dates, authors, commit messages, etc.
  • We converted the sources files in order to make them Git compliant (authors files generation, file encoding clean up, etc…) running Java scripts through a JAR dedicated to SVN/Git migration (downloadable on the migration tutorial)
  • We created a Bitbucket account for the Valiantys developers team and created the 4 Git repositories
  • Finally, we pushed the sources to Bitbucket for each project

We struggled with some of these steps, but thanks to Joseph Clark (@jaysee00), it’s finally done ! 🙂

Bitbucket / Git – Getting started

For us developers, we had to learn the basics of using Git. It took us some time to adapt, but we already see what’s great about Git: with the staging area, we can all work on our developments without blocking each other.

It will be interesting to give you some feedback in a few months and tell you if we plan to migrate our commercial products as well 😉

Related resources

View all resources