Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
DevOps Culture and Practice with OpenShift

You're reading from  DevOps Culture and Practice with OpenShift

Product type Book
Published in Aug 2021
Publisher Packt
ISBN-13 9781800202368
Pages 812 pages
Edition 1st Edition
Languages
Concepts
Authors (5):
Tim Beattie Tim Beattie
Profile icon Tim Beattie
Mike Hepburn Mike Hepburn
Profile icon Mike Hepburn
Noel O'Connor Noel O'Connor
Profile icon Noel O'Connor
Donal Spring Donal Spring
Profile icon Donal Spring
Ilaria Doria Ilaria Doria
Profile icon Ilaria Doria
View More author details
Toc

Table of Contents (30) Chapters close

Preface Acknowledgements Section 1: Practices Make Perfect
1. Introduction — Start with Why 2. Introducing DevOps and Some Tools 3. The Journey Ahead Section 2: Establishing the Foundation
4. Open Culture 5. Open Environment and Open Leadership 6. Open Technical Practices – Beginnings, Starting Right 7. Open Technical Practices — The Midpoint Section 3: Discover It
8. Discovering the Why and Who 9. Discovering the How 10. Setting Outcomes Section 4: Prioritize It
11. The Options Pivot Section 5: Deliver It
12. Doing Delivery 13. Measure and Learn Section 6: Build It, Run It, Own It
14. Build It 15. Run It 16. Own It Section 7: Improve It, Sustain It
17. Improve It 18. Sustain It Index
Appendix A – OpenShift Sizing Requirements for Exercises 1. Appendix B – Additional Learning Resources

7. Open Technical Practices — The Midpoint

In this chapter, we are going to build on the foundational technical practices that we started in the previous chapter. We will acquire a shared understanding of our software delivery pipeline using the Big Picture practice. Even the less technical team members will be able to follow what happens to our software as it is being written and delivered.

We will then explain a technique that allows DevOps teams to deliver software changes using Git as the driving tool. The practice of GitOps leads to greater visibility of changes within our system, allowing the team to debug and resolve issues faster. We will explore how to improve our code quality through test automation and conclude this chapter by asking the question How do we know if our architecture is good?

This chapter will cover the following topics:

  • The Big Picture
  • GitOps
  • Testing
  • Emerging architecture
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €14.99/month. Cancel anytime}