Infrastructure as Code – Branches

Recently has a read of Infrastructure as Code.  One particular topic that is worth calling out is Chapter 10, Software Engineering Practices for Infrastructure.  In particular, the “branch” discussion 🙂

Page 183 clarifies the view that numerous teams have with branches:

Rather than continuously integrating changes, many development teams commit changes to separate branches in their VCS.  The goal is usually to allow people to spend time finishing a large change before they worry about making it work with any change that other people are working on

This leads nicely into Codebase Organization Patterns, page 267, and the Antipattern: Branch-Based Codebases, and the great sub title, “Workflow Effectiveness” 🙂

Page 196 provide another good read on testing, and why separate teaming and engineering teams is wrong.


~ by mdavey on June 30, 2016.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: