DVCS systems have become popular amongst agile developers over the past few years. However they have mainly lived either in open source projects (often hosted on GitHub or BitBucket) or on smaller teams that would then promote code into the “authorized” or corporate repository. DVCS systems provide advantages in performance for branch and merge operations thus enabling a smoother workflow during refactoring and with teams that may be distributed. The key challenge has been a lack of enterprise tooling to both understand code evolution/history and more importantly support for user access control.
Over the last 6 months we have seen significant investment into support for Git and Mercurial and other vendors who have been delivering commercial DVCS systems (e.g. PlasticSCM). 3 key examples include:
- Accurev – Kando lets you visual branching and process, and provide access control and lets Git repositories to run and be managed in parallel with Accrev native repositories
- Collabnet – has integrated Git to TeamForge providing authentication, a master repository, and life-cycle integration
- Atlassian – new Git-based Stash product provides user and repository management and code traceability between Jira issues and changesets
This growing support will speed migration for organizations that currently use Subversion but are struggling with branch/merge overhead.
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
The Mobile Scenario: Taking Mobility to the Next Level
The definition of "mobile" in the post-app era will involve new interactions such as bots and conversations, new devices such as wearables...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.