December 28, 2015
Manage Your Repo for Success with Git in the Enterprise
Git at Scale
Email sign up
Throughout this series of posts, we are examining some of the challenges faced when adopting Git in the enterprise space, and presenting tips and best practices for successfully managing the task. This installment covers repository management and avoiding Git sprawl.
The need for repository management varies greatly depending upon the limitations of your chosen Git management solution. If you choose a system that poorly handles digital assets, large numbers of files, or a large total repository size, then Git sprawl may be your new way of life.
Similarly, you may also incur Git sprawl if your process relies heavily on component-based development (CBD). Large numbers of individually developed and versioned components can lead to issues with Git “submodules” if your Git management solution doesn’t provide another mechanism. Git by itself makes it relatively easy to map external repositories into another, but there are a number of different tools, approaches, and trade-offs to consider.
Regardless of the cause, the more finely you have to break apart your content, the more problems you’ll have trying to put it back together for builds, testing, and other tasks. Managing the explosion of repositories can become a full-time DevOps headache without careful planning and maintenance.
Repository Management Best Practices
The previous posts in this series are GitSwarm: Your Questions Answered, Narrow Cloning with GitSwarm, GitSwarm + Helix: Unity through Diversity, Reliability for Git in the Enterprise, and Stay Secure for Success with Git in the Enterprise. In our next, and final, installment, we’ll tackle the need for transparent visibility into the production pipeline. For the complete set of Git in the Enterprise tips and best practices, download our free eBook.