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.
About Site Reliability Engineering:
This book is a collection of essays and articles written by key members of Google’s Site Reliability Teams (SRT). You’ll learn the principles and practices that enable Google engineers to make systems more scalable, reliable, and efficient—lessons you can apply directly to your organization.
Table of contents
- The Role of a Release Engineer
- Continuous Build and Deployment
- Configuration Management
- Title: Release Engineering
- Release date: June 2016
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 9781491965214
You might also like
51+ hours of video instruction. Overview The professional programmer’s Deitel® video guide to Python development with …
Fluent Python, 2nd Edition
Python’s simplicity lets you become productive quickly, but often this means you aren’t using everything it …
Data Science from Scratch, 2nd Edition
To really learn data science, you should not only master the tools—data science libraries, frameworks, modules, …
Microservices: Up and Running
Microservices architectures offer great benefits: faster change speeds, better scalability and cleaner, evolvable architectures. But, implementing …