Home » Technical » Migrating from Subversion and Trac to Gitlab

Migrating from Subversion and Trac to Gitlab

posted in: Technical 0

3DN has been using Trac and Subversion for a very long time. We’ve built up considerable expertise. However, with Devops and CI/CD pipelines pushing through on the Cloud immensely, we felt it was time we looked into migrating from Trac to Gitlab and use Git as our primary means of version control.

From project planning and source code management to CI/CD and monitoring, GitLab is a complete DevOps platform, delivered as a single application. Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance.

We have found the migration to be quite painless. While it takes some time to get used to Gitlab vs. Trac, on the whole it is so much more loaded with features that the things missing in Gitlab at first looks can often be implemented in other ways.

Git itself is a whole different story however. While it’s nimble and fast, the differences with Subversion are incredible. Setting up an internal process to deal with Git vs. Subversion will take a long time. With Subversion becoming more and more irrelevant however, it’s also a step that any company should take.

Leave a Reply

Your email address will not be published. Required fields are marked *