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

Using npm packages with Actions

It is very easy to set up a release workflow for packages with GitHub Actions. You can use GITHUB_TOKEN to authenticate and the native clients of your package managers. To try it out with npm, you can follow the step-by-step instructions here: https://github.com/wulfland/package-demo.

You can create the package using npm init if you have installed npm on your machine. Otherwise, just copy the contents of package.json and package-lock.json from the aforementioned repository.

The workflow to publish the package is simple. It gets triggered every time a new release is created:

on:
  release:
    types: [created]

The workflow consists of two jobs. The first one only builds and tests the package using npm:

  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
     ...