Book Image

DevOps Culture and Practice with OpenShift

By : Tim Beattie, Mike Hepburn, Noel O'Connor, Donal Spring, Ilaria Doria
Book Image

DevOps Culture and Practice with OpenShift

By: Tim Beattie, Mike Hepburn, Noel O'Connor, Donal Spring, Ilaria Doria

Overview of this book

DevOps Culture and Practice with OpenShift features many different real-world practices - some people-related, some process-related, some technology-related - to facilitate successful DevOps, and in turn OpenShift, adoption within your organization. It introduces many DevOps concepts and tools to connect culture and practice through a continuous loop of discovery, pivots, and delivery underpinned by a foundation of collaboration and software engineering. Containers and container-centric application lifecycle management are now an industry standard, and OpenShift has a leading position in a flourishing market of enterprise Kubernetes-based product offerings. DevOps Culture and Practice with OpenShift provides a roadmap for building empowered product teams within your organization. This guide brings together lean, agile, design thinking, DevOps, culture, facilitation, and hands-on technical enablement all in one book. Through a combination of real-world stories, a practical case study, facilitation guides, and technical implementation details, DevOps Culture and Practice with OpenShift provides tools and techniques to build a DevOps culture within your organization on Red Hat's OpenShift Container Platform.
Table of Contents (30 chapters)
Free Chapter
2
Section 1: Practices Make Perfect
6
Section 2: Establishing the Foundation
11
Section 3: Discover It
15
Section 4: Prioritize It
17
Section 5: Deliver It
20
Section 6: Build It, Run It, Own It
24
Section 7: Improve It, Sustain It
27
Index
Appendix B – Additional Learning Resources

14. Build It

"It works on my machine"—a phrase heard time and time again by developers, testers, and operators as they write, test, and verify their code. It works on my machine is a phrase rooted in siloed teams where ownership of the problem moves around like a tennis ball on a court at Wimbledon. The metaphorical wall that exists between teams that have operated in silos, passing work over the wall and not taking full responsibility for the end-to-end journey is a problem that has been around for decades. We need to break away from this behavior! From now on, it's not, "It's working on my machine" but rather, "How has your code progressed in the build system?" The build and deployment pipeline our code runs through is a shared responsibility. In order for this to be the case, all team members must contribute to the pipeline and be ready to fix it when it breaks.

Figure 14.1: It works on my machine

...