The DevOps Handbook – Architecting for Low-Risk Releases

Our journey into the world of DevOps continues with The DevOps Handbook as Michael doesn't take enough tangents, Joe regrets automating the build, err, wait never regrets (sorry), and ducks really like Allen.

If you're reading these show notes via your podcast player, you can find this episode's full show notes at https://www.codingblocks.net/episode137, where you can be a part of the conversation.

Sponsors

• Datadog – Sign up today for a free 14 day trial and get a free Datadog t-shirt after your first dashboard.
• Secure Code Warrior – Start gamifying your organization's security posture today, score 5,000 points, and get a free Secure Code Warrior t-shirt.

Survey Says

What is your meeting limit?

Take the survey at: https://www.codingblocks.net/episode137.

News

• Thank you to everyone that left us a new review!
  • iTunes: justsomedudewritingareview, stupub, andrew.diamond, scipiomarcellus
  • Stitcher: Bicycle Repairman, BrunoLC
• Using Bazel to build and test software of any size, quickly and reliably. (bazel.build)
• Reflections on Trusting Trust (cs.cmu.edu)
• Build your own Linux distro! (linuxfromscratch.org)
• That System76 Oryx Pro keyboard though? (System76)

Fast, Reliable. Pick Two

Continuously Build, Test, and Integrate our Code and Environments

• Build and test processes run constantly, independent of coding.
• This ensures that we understand and codify all dependencies.
• This ensures repeatable deployments and configuration management.
• Once changes make it into source control, the packages and binaries are created only ONCE. Those same packages are used throughout the rest of the pipeline to ensure all environments are receiving the same bits.
• What does this mean for our team culture?
  • You need to maintain reliable automated tests that truly validate deploy-ability.
  • You need to stop the "production pipeline" when validation fails, i.e. pull the andon cord.
  • You need to work in small, short lived batches that are based on trunk. No long-lived feature branches.
    • Short, fast feedback loops are necessary; builds on every commit.

Integrate Performance Testing into the Test Suite

• Should likely build the performance testing environment at the beginning of the project so that it can be used throughout.
• Logging results on each run is also important. If a set of changes shows a drastic difference from the previous run, then it should be investigated.

Enable and Practice Continuous Integration

• Small batch an