You're reading from Embracing DevOps Release Management Strategies and tools to accelerate continuous delivery and ensure quality software deployment

Product type Paperback

Published in Apr 2024

Publisher Packt

ISBN-13 9781835461853

Length 350 pages

Edition 1st Edition

Tools

Construct

Concepts

Continuous Delivery

Author (1):

Joel Kruger

Preface

1. Part 1: Understanding the Software Development Life Cycle and Its Design

2. Chapter 1: Understanding the Software Development Life Cycle FREE CHAPTER

3. Chapter 2: A Brief Introduction to Release Management

4. Chapter 3: What Are the Various SDLC Release Management Models?

5. Part 2: The Advantages of DevOps Release Management

6. Chapter 4: What Problems Does DevOps Release Management Try to Solve?

7. Chapter 5: Understanding What Makes DevOps Release Management Unique

8. Chapter 6: Understanding the Basics of CI/CD

9. Chapter 7: A Practical Pipeline for Technical Release Managers

10. Chapter 8: How CI/CD Pipelines Enforce Good DevOps Release Management

11. Part 3: Develop a Culture of DevOps in Your Organization’s Release Management Strategy

12. Chapter 9: Embracing DevOps Culture in Your Release Management Strategy

13. Chapter 10: What Does Receiving Support from Leadership and Stakeholders Look Like?

14. Chapter 11: Overcoming Common Pitfalls in DevOps Release Management

15. Index

16. Other Books You May Enjoy

Appendix

Questions

Answer the following questions to test your knowledge of this chapter:

What are each of the OWASP Top 10 CI/CD Security Risks?
What are the three common paths to CI/CD governance?
What is the significance of mapping CI/CD systems and processes? What term described this process?
What are the four most common branching strategies used by development teams today?
What is the difference between trunk-based development and scaled trunk development?
Which of the four branching strategies described in this chapter promote feature-driven development?
What is the difference between a release pipeline and a deployment pipeline?
What is the difference between an artifact store and a configuration store?
Why are external CCBs and CABs frequently cited as an anti-pattern in the context of DevOps release management?
Why is it considered good practice to implement methods that move validation steps into the development platform?

The rest of the chapter is locked