Название: Trunk-Based Development And Branch By Abstraction
Автор: Paul Hammant
Издательство: Leanpub
Год: 2020-08-05
Страниц: 367
Язык: английский
Формат: pdf (true), epub
Размер: 25.0 MB

Trunk-based development and branch by abstraction super reference. All the aspects of this industry leading branching model covered.

An all you need to know reference book about trunk-based development, Branch by abstraction and related software development practices. Many diagrams throughout, and a sections on working out how your company can get from where you are to trunk-based development, CI, CD and all that comes with it.

Trunk-Based Development is a strategy for controlling software development in which developers collaborate on code in a single shared branch called ‘trunk’. Its aim is to overcome the perennial problem where multiple concurrent changes to large scale software programs may temporarily invalidate the whole. All commits are written back to this trunk, and developers must resist any pressure to create other long-lived development branches by employing a number of documented techniques. Therefore, every commit still produces a production-ready build. There is only one branch available to the developers for their collaboration, the ‘trunk’.

Trunk-Based Development is not a new branching model. The word ‘trunk’ refers to the concept of a growing tree, where the fattest and longest span is the trunk, not the branches which radiate from it and are of a more limited length. It has been a lesser known branching model of choice since the mid-nineties and considered tactically since the eighties. The largest of development organizations, like Google (as mentioned) and Facebook practice it at scale. Over the past 30 years different advances to source-control technologies and related tools/techniques have made Trunk-Based Development more (and occasionally less) prevalent, but it has been a branching model which has retained many loyal users through the years.