You're reading from Accelerate DevOps with GitHub Enhance software delivery performance with GitHub Issues, Projects, Actions, and Advanced Security

Product type Paperback

Published in Sep 2022

Publisher Packt

ISBN-13 9781801813358

Length 540 pages

Edition 1st Edition

Tools

GitHub

Concepts

DevOps

Author (1):

Michael Kaufmann

View More author details

Table of Contents (31) Chapters

Preface

1. Part 1: Lean Management and Collaboration

2. Chapter 1: Metrics That Matter FREE CHAPTER

3. Chapter 2: Plan, Track, and Visualize Your Work

4. Chapter 3: Teamwork and Collaborative Development

5. Chapter 4: Asynchronous Work: Collaborate from Anywhere

6. Chapter 5: The Influence of Open and Inner Source on Software Delivery Performance

7. Part 2: Engineering DevOps Practices

8. Chapter 6: Automation with GitHub Actions

9. Chapter 7: Running Your Workflows

10. Chapter 8: Managing Dependencies Using GitHub Packages

11. Chapter 9: Deploying to Any Platform

12. Chapter 10: Feature Flags and the Feature Lifecycle

13. Chapter 11: Trunk-Based Development

14. Part 3: Release with Confidence

15. Chapter 12: Shift Left Testing for Increased Quality

16. Chapter 13: Shift-Left Security and DevSecOps

17. Chapter 14: Securing Your Code

18. Chapter 15: Securing Your Deployments

19. Part 4: Software Architecture

20. Chapter 16: Loosely Coupled Architecture and Microservices

21. Chapter 17: Empower Your Teams

22. Part 5: Lean Product Management

23. Chapter 18: Lean Product Development and Lean Startup

24. Chapter 19: Experimentation and A|B Testing

25. Part 6: GitHub for your Enterprise

26. Chapter 20: GitHub – The Home for All Developers

27. Chapter 21: Migrating to GitHub

28. Chapter 22: Organizing Your Teams

29. Chapter 23: Transform Your Enterprise

30. Other Books You May Enjoy

Case study

The two pilot teams at Tailwind Gears have achieved a much higher delivery lead time and deployment frequency thanks to the DevOps practices that have been applied. The mean time to restore is also much better because the release pipelines help ship fixes faster. However, the change failure rate has dropped. Releasing more frequently also means that more deployments fail and finding bugs in the code is hard. The quality signals that come from the automated test suites are just not reliable enough and fixing one bug often introduces another bug in another module. There are still many parts of the application that need manual testing – but with one QA engineer in the team, this was not an option. So, some of these parts have been replaced with UI tests, while others have just been dropped.

To evaluate the test portfolio, the teams must introduce a test taxonomy and include reporting in their pipelines. The QA engineers in the team are responsible for the taxonomy...