Book Image

Accelerate DevOps with GitHub

By : Michael Kaufmann
Book Image

Accelerate DevOps with GitHub

By: Michael Kaufmann

Overview of this book

This practical guide to DevOps uses GitHub as the DevOps platform and shows how you can leverage the power of GitHub for collaboration, lean management, and secure and fast software delivery. The chapters provide simple solutions to common problems, thereby helping teams that are already on their DevOps journey to further advance into DevOps and speed up their software delivery performance. From finding the right metrics to measure your success to learning from other teams’ success stories without merely copying what they’ve done, this book has it all in one place. As you advance, you’ll find out how you can leverage the power of GitHub to accelerate your value delivery – by making work visible with GitHub Projects, measuring the right metrics with GitHub Insights, using solid and proven engineering practices with GitHub Actions and Advanced Security, and moving to event-based and loosely coupled software architecture. By the end of this GitHub book, you'll have understood what factors influence software delivery performance and how you can measure your capabilities, thus realizing where you stand in your journey and how you can move forward.
Table of Contents (31 chapters)
1
Part 1: Lean Management and Collaboration
7
Part 2: Engineering DevOps Practices
14
Part 3: Release with Confidence
19
Part 4: Software Architecture
22
Part 5: Lean Product Management
25
Part 6: GitHub for your Enterprise

Case study

The first thing our two pilot teams at Tailwind Gears do is move their code over to a GitHub repository. One team is already using Git on a Bitbucket server. For that team, the migration is as easy as pushing the repository to a new remote. The other team is using Team Foundation Server (TFS) version control and must migrate the code to Git first on the server before pushing it to GitHub.

Both teams decide to participate in 2-day Git training to be able to leverage the full power of Git and craft good commits that are easy to review. They use draft pull requests so that everyone in the team always knows what the others are working on, and they set a minimum of two required reviewers for the time being.

Many of the work is still outside the repositories and happens in Word, Excel, and Visio documents that are stored on the company SharePoint server. Some of the documents are converted to Portable Document Format (PDF) and are signed off by management before releasing...