The decision of your organization to adopt enterprise Git as a corporate source code management (SCM) standard is not merely a technical concern. It also has a major impact on the business performance of your organization. To effectively address the challenges of enterprise Git adoption, organizations should set the bar high by handling Git as a strategic investment.
In order to be successful with implementing Git in the enterprise, be sure to select an Enterprise Version Control (EVC) platform for centralized, distributed and hybrid development environments. This platform must also integrate with existing development tools enabling Continuous Integration (CI) and Continuous Delivery (CD).
Here are the top 4 challenges of Enterprise Git adoption:
(1) Insufficient native access and audit controls in Git
Git was designed for the needs of open source projects, specifically Linux. It can reliably track who authored a change and who can add changes to a repository. While sufficient for most open source projects, this design consideration left out many of the inherent security controls of centralized version control tools, such as Subversion (SVN), which is currently used by the enterprise. This realization often comes as a shock to security and compliance officers in large companies once they discover the risks associated with migration from centralized legacy SCM to Git.
(2) Heterogeneity of modern enterprise development infrastructure
As long as hybrid SCM is still the norm, there is a need to manage Git and SVN simultaneously—not only within the enterprise but also at the individual project level. However, most Git solutions in the market today ignore this need completely and do not provide any management or governance for anything except Git itself. As a result, organizations often experience difficulties articulating their SVN/Git infrastructure coexistence strategy or face an “all or nothing” migration dilemma.
(3) Avoiding disruption of existing business processes
Large companies are very sensitive to “deregulation” permitted by Git’s powerful branching capabilities as it potentially may cause a lot of changes in the company’s existing software delivery lifecycle management processes, causing disruption to automated integration, build, and delivery infrastructure investments. These concerns are legitimate, and stakeholders across the organizations need to have a means to preserve existing investments and replicating the company’s current business processes.
(4) Need to maintain highly distributed, federated repositories
While the use of a central master repository (also referred to as a “golden,” “canonical,” or “blessed” repository) is easier to manage, Git does not mandate this approach. For the enterprise, however, federated deployments pose a serious risk of intellectual property or data loss. With dozens or hundreds of servers, it becomes challenging to locate code or enforce strategies for backup, disaster recovery, or failover.
Interested in learning how CollabNet can help you be successful implementing Git in the enterprise?
Try CollabNet’s TeamForge SCM solution free for 30 days! TeamForge SCM is an Enterprise Version Control platform that gives organizations the advantages of distributed (Git) or centralized (SVN) version control systems, while ensuring compliance, governance, and IP security across all source code-related activities.
About the AuthorMore Content by Miikka Andersson