Build Status workflow (dagrejs/dagre-d3)

The Build Status workflow from dagrejs/dagre-d3, explained and optimized by Latchkey.

What it does

This is the Build Status workflow from the dagrejs/dagre-d3 repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

name: Build Status

on:
  push:
  pull_request:

jobs:
  build:
    runs-on: ${{ matrix.os }}

    strategy:
      matrix:
        os: [ubuntu-latest]
        node-version: [12.x]

    steps:
    - uses: actions/checkout@v2
    - uses: browser-actions/setup-firefox@latest

    - name: Use Node.js ${{ matrix.node-version }}
      uses: actions/setup-node@v1
      with:
        node-version: ${{ matrix.node-version }}

    - name: Install dependencies
      run: |
        npm install
        sudo apt-get install graphviz xvfb

    - name: Lint
      run: |
        make lint

    - name: Test
      run: |
        KARMA_OPTS="--browsers Firefox" xvfb-run --auto-servernum make -e test

The same workflow, on Latchkey

Estimated ~20% faster on cache hits, plus fewer wasted runs and a safer supply chain. Added and changed lines are highlighted.

name: Build Status
 
on:
  push:
  pull_request:
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    timeout-minutes: 30
    runs-on: ${{ matrix.os }}
 
    strategy:
      matrix:
        os: [ubuntu-latest]
        node-version: [12.x]
 
    steps:
    - uses: actions/checkout@v2
    - uses: browser-actions/setup-firefox@latest
 
    - name: Use Node.js ${{ matrix.node-version }}
      uses: actions/setup-node@v1
      with:
        cache: 'npm'
        node-version: ${{ matrix.node-version }}
 
    - name: Install dependencies
      run: |
        npm install
        sudo apt-get install graphviz xvfb
 
    - name: Lint
      run: |
        make lint
 
    - name: Test
      run: |
        KARMA_OPTS="--browsers Firefox" xvfb-run --auto-servernum make -e test
 

What changed

• Cancel superseded runs when a branch or PR gets a newer push.
• Cache dependency installs on the setup step so they are served from cache.
• Add a job timeout so a hung step cannot burn hours of runner time.

1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.

What Latchkey heals here

This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:

• Dependency installs

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow