Archives for the tag: svn

From SVN to Git: How Atlassian Made the Switch Without Sacrificing Active Development – the Human Side

This post was featured in Dr. Dobb’s as part of a series focusing on enterprise teams making the switch to Git. In this three part blog series we focus on migrating the JIRA code base from Subversion to Git. We wanted to share our migrating experience to those of you who are contemplating moving a large project to Git - without sacrificing active development. In our first post we discuss why we decided to make the switch to Git. In our second post we dive in the technical details of switching

Continue reading »

Tags: , , , , ,
Comments (8)

From SVN to Git: How Atlassian Made the Switch Without Sacrificing Active Development – the Technical Side

Featured on Dr. Dobb's, this is the second blog in a three part series about making the switch to Git in the enterprise. In the first post, we discussed why so many teams today have decided to make the switch. This post focuses on the technical aspects of how Atlassian actually made the switch to Git. In this three part blog series I will focus on the biggest migration Atlassian has done – migrating the 11-year-old JIRA codebase from SVN to Git. What obstacles did we encounter? What lessons did

Continue reading »

Tags: , , , , ,
Comments (15)

From SVN to Git: How Atlassian Made the Switch Without Sacrificing Active Development

This post was featured in Dr. Dobb's as part of a series focusing on enterprise teams making the switch to Git. At Atlassian, we have been extremely excited about DVCS for a number of years. We have invested heavily in DVCS. We acquired Bitbucket - a cloud DVCS repository host. We developed Stash - a behind the firewall Git repository manager. We added DVCS support to FishEye, our code browsing and search tool. And we added a myriad of DVCS connectors to JIRA, our issue tracker. We believe DVCS

Continue reading »

Tags: , , , ,
Comments (22)

FishEye and Crucible 2.9 Released: Simplified Administration, Stronger JIRA Integration

Today we are pleased to announce the latest release of FishEye and Crucible. FishEye and Crucible give agile teams a powerful way to browse, search, share and review source code. Tight integration with the JIRA issue tracker gives teams traceability between issues, stories and source, regardless of your source code management system(s) – Git, Subversion, CVS, Mercurial or Perforce. FishEye 2.9 and Crucible 2.9 have improved integration with JIRA, enabling development teams to move faster and

Continue reading »

Tags: , , , , , , , ,
Comments (10)

Making the Switch to DVCS: The FishEye Teams move from Subversion to DVCS

The Tool is the Easy Part - What about the Processes? The FishEye team was the first team at Atlassian to make the switch to DVCS, and while some Atlassians had previous DVCS experience, quite a few had not yet used it in the workplace with a medium-size team of developers before. We looked for help around the web, but there wasn't a lot of people sharing their experiences at the time. We found many resources like "How do I push a branch in Git?" or "How do I pull from multiple remotes in Mercurial?",

Continue reading »

Tags: , , , , , , , , , , , , ,
Comments (4)

FishEye Release Report 2: You Want to Merge What?

The last time I introduced the FishEye Release Report, we focused on how it can show you which JIRA issues are included in your new release based on the source, rather than based on what your developers enter manually into JIRA. Furthermore, the Release Report summarizes important information about those JIRA issues, such as their Fix Versions and relevant code reviews. We find these features alone make the plugin really useful, but we have one other high value use for the Release Report that might

Continue reading »

Tags: , , , , , ,
Comments (0)