September 23, 2015

Seven Tips for Success with Git in the Enterprise

Git at Scale

Making Git work in the enterprise is neither easy nor obvious. In fact, its adoption creates a number of challenges to balance developer preferences with enterprise needs.

To learn about the challenges, and get practical tips and best practices to solve the challenges, download the eBook: Seven Tips for Success with Git in the Enterprise. Said eBook explores seven considerations for using Git in the enterprise.


The most obvious reason for Git adoption is that developers prefer its distributed workflow, even though it’s rarely used in an entirely distributed model. But once you move beyond the individual desktop, how do you manage the new complexity introduced by Git?


A popular dictum of Agile development is that you should keep all of your intellectual property in the same place, a “single source of truth.” Yet increasingly, multi­disciplinary teams and requirements have exploded the sheer number and size of assets for a typical project. How do you handle Git adoption when its capabilities mandate a practical maximum repository size of a gigabyte or two at most?


Whatever workflows your contributors favor or type of content they create, the final products have to be integrated and tested with as much automation as possible. The architecture of Git can make this a heavy load on build systems. What are you doing to get reasonable performance from continuous delivery systems?


No matter how well a tool does a job, it’s not useful when it’s not working. This is especially true in the enterprise, which often runs around the clock around the world. Git was built largely with the simple file system in mind, and most Git management solutions are built directly on top of basic Git. Are you meeting your requirements for disaster recovery and high availability?


Raw Git has a limited approach to security, providing solid authentication while ignoring authorization altogether. This approach is great if all you want to do is ensure each commit author is who he or she claims to be because identity is verified through the use of public­key cryptography signatures. But what if you want to restrict access to a particular repository? A particular branch? How about a single file full of proprietary secrets? How do you secure your most crucial assets with Git?


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. What are your plans to tame it?


Most Git management solutions do little (if anything) to address the need for transparent visibility into the production pipeline at every stage. When embracing Git, are you going to be on your own handcrafting plugins, scripts, or other integration mechanisms?

To get the whole story plus best practices for each consideration, download the eBook, Seven Tips for Success with Git in the Enterprise.