Release engineering is a relatively new and fast-growing discipline for building and delivering software. Release engineers at Google, for instance, use knowledge of development, configuration management, test integration, system administration, and customer support to compile, assemble, and deliver source code into software components or finished products.
With this excerpt from O’Reilly’s Site Reliability Engineering, you’ll learn how Google’s approach can inform your own company’s release engineering process—regardless of company size or the tools you use. Google Release Team member Dinah McNutt explains the rationale behind the company’s release engineering philosophy of self-sufficient teams, frequent (often-hourly) releases, and a self-contained build process that depends on known versions of build tools and dependencies.
You’ll discover a proven process for manufacturing software that is repeatable, gives predictable results, scales well, and can contribute to the growth of your company.
Author(s): Dinah McNutt; Betsy Beyer
Publisher: O'Reilly
Year: 2016
Language: English
Pages: 19
Cover
Web Ops
Copyright
Table of Contents
Chapter 1. Release Engineering
The Role of a Release Engineer
Philosophy
Self-Service Model
High Velocity
Hermetic Builds
Enforcement of Policies and Procedures
Continuous Build and Deployment
Building
Branching
Testing
Packaging
Rapid
Deployment
Configuration Management
Conclusions
It’s Not Just for Googlers
Start Release Engineering at the Beginning
About the Author and Editors