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

Monitoring and troubleshooting

If you have problems with your self-hosted runners, there are several things that can help you when troubleshooting.

Checking the status of the runners

You can check the status of your runners under Settings | Actions | Runners. The status of a runner can be Idle, Active, or Offline. If the runner status is Offline, the machine could be down or not connected to the network, or the self-hosted runner application might not be running on the machine.

Reviewing the application log files

Log files are kept on the runner in the _diag folder in the runner's root directory. You can review the runner application log files in _diag. The application log filenames begin with Runner_ and have a UTC timestamp appended to them:

Runner_20210927-065249-utc.log

Reviewing the job log files

The job log files are also located in _diag. Each job has its own log. The application log filenames begin with Worker_ and also have a UTC timestamp appended...