Continuous Delivery and DevOps - a Quickstart Guide : Start Your Journey to Successful Adoption of CD and DevOps, 3rd Edition.
Continuous Delivery (CD) and DevOps are fast establishing themselves as the next big-ticket investment in the world of software delivery. Delivering quality software can be very painful and expensive. This book will help you demystify what it takes to effectively adopt Continuous Delivery (CD) and D...
Clasificación: | Libro Electrónico |
---|---|
Autor principal: | |
Formato: | Electrónico eBook |
Idioma: | Inglés |
Publicado: |
Birmingham :
Packt Publishing Ltd,
2018.
|
Edición: | 3rd ed. |
Temas: | |
Acceso en línea: | Texto completo |
Tabla de Contenidos:
- Cover; Title Page; Copyright and Credits; Packt Upsell; Contributors; Table of Contents; Preface; Chapter 1: The Evolution of Software Delivery; ACME systems
- evolution phase 1.0; Software-delivery process flow Version 1.0; ACME systems evolution phase 2.0; Software-delivery process flow Version 2.0; An outsider's perspective from the inside; ACME systems evolution phase 3.0; Software-delivery process flow version 3.0; ACME systems beyond Version 3.0; The evolution in a nutshell; Where am I on the evolutionary scale?; Summary; Chapter 2: Understanding Your Current Pain Points
- Elephant in the roomDefining the rules; Including (almost) everyone; Identifying key people; Too many cooks; Openness, transparency, and honesty; Secrets hiding the truth; Location, location, location; It's all happy-clappy management waffle
- isn't it?; The great elephant disclosure; Tools and techniques to expose the obvious; Timeline; Value stream mapping; Summary; Chapter 3: Culture and Behaviors are the Cornerstones to Success; All roads lead to culture; Defining culture; Processes; Communications; Tools and techniques; An open, honest, and safe environment; Openness and honesty
- Courageous dialogueThe physical environment; Encouraging and embracing collaboration; Fostering innovation and accountability at a grass-roots level; The blame game; Blame slowly, learn quickly; Building trust-based relationships across organizational boundaries; Rewarding good behaviors and success; The odd few; Recognizing how Dev and Ops teams are incentivized can have an impact; Embracing change and reducing risk; Changing people's perceptions with pudding; Being transparent; Summary; Chapter 4: Planning for Success; Some common problems; Setting and communicating goals and vision
- Standardizing vocabulary and languageA business change project in its own right; Dev + Ops + Org; The pros and cons of a dedicated team; The importance of evangelism; The courage and determination required throughout the organization; Understanding the cost; Seeking advice from others; Summary; Chapter 5: Approaches, Tools, and Techniques; Engineering best practices; Source-control; The binary repository; Small, frequent, and simple changes; Automated builds; Test-automation; Continuous integration; Fail fast and often; Architectural approaches; Component-based architecture
- Layers of abstractionNever break your consumer; Open and honest peer-working practices; Incremental delivery of features; Using the same binary across all environments; How many environments is enough?; Developing against a like-live environment; CD and DevOps tooling; Automated provisioning; No-downtime deployments; Monitor, monitor, monitor; When a simple manual process is also an effective tool; Summary; Chapter 6: Avoiding Hurdles; What are the potential issues you need to look out for?; Dissenters in the ranks; No news is no news; The change curve; The outsiders