Agile + DevOps West 2020 Concurrent Session : Lessons Learned Moving to Trunk Based Development


Thursday, June 11, 2020 - 4:45pm to 5:45pm

Lessons Learned Moving to Trunk Based Development

Add to calendar

Moving from a branching model, such as GitFlow, to “trunk dev” (Trunk-Based Development) isn't trivial and isn't easy, but it is definitely worth the effort if increasing release velocity is your goal. Craig Sebenik led the transition to “trunk dev” at a couple of companies after being involved in a massive project at LinkedIn. Join Craig as he describes "trunk dev" and gives his perspective on the scenarios where the different flavors work best. Discuss what you loose by moving away from a branching model and what you gain with "trunk dev" and why that transition will set up for team for future growth and faster development cycles. (Note that the talk will focus on Git however, the general concepts should work for other SCM systems.) Leave the talk with some examples of where various schemes excel, the pros and cons of "trunk dev" itself, and what you can expect during a transition from a branching model to "trunk dev". Moving to Trunk Based Development isn't always easy, but after doing it a few times, Craig is happy to help smooth out the road for others.

Craig Sebenik
Split Software

Craig Sebenik has been an SRE at several startups and at LinkedIn. His greatest passion is teaching what he has learned from adventures in SRE/DevOps and cooking. Cooking will have to wait for an open space or hallway track :-) Craig has authored O'Reilly books on SaltStack (SaltStack Essentials) and SRE (What is SRE?). He has spoken at several conferences, including SaltConf, SREcon, and LISA. He has also been featured on Split’s Espresso With The Evangelist webcast explaining Trunk Based Development. He enjoys automating routine tasks and allowing computers to come up to their full potential to reduce boring work. He has been programming for over 40 years and has worked in a number of languages, including C, JAVA, Perl, and FORTRAN. (He has even worked with COBOL. But, don't hold that against him.)