ci workflow (restify/node-restify)
The ci workflow from restify/node-restify, explained and optimized by Latchkey.
CI health: D - needs work
Point runs-on at Latchkey and get caching, run de-duplication, job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the ci workflow from the restify/node-restify 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
on:
push:
branches:
- master
pull_request:
branches:
- master
name: ci
jobs:
lint:
name: lint
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: install node v16
uses: actions/setup-node@v1
with:
node-version: v16.x
- name: install dependencies
run: npm install
- name: check lint
run: make check-lint
test:
name: test node ${{ matrix.node-version }} on ${{ matrix.os }}
strategy:
fail-fast: false
matrix:
os:
- ubuntu-latest
node-version:
- 14.x
- 16.x
- 18.x
- 20.x
runs-on: ${{matrix.os}}
steps:
- uses: actions/checkout@v2
- name: use node ${{ matrix.node-version }}
uses: actions/setup-node@v1
with:
node-version: ${{ matrix.node-version }}
- name: install dependencies
run: npm install
- name: test
run: make test
env:
TEST_SKIP_IP_V6: true
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.
on: push: branches: - master pull_request: branches: - master name: ci concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: lint: timeout-minutes: 30 name: lint runs-on: latchkey-small steps: - uses: actions/checkout@v2 - name: install node v16 uses: actions/setup-node@v1 with: cache: 'npm' node-version: v16.x - name: install dependencies run: npm install - name: check lint run: make check-lint test: timeout-minutes: 30 name: test node ${{ matrix.node-version }} on ${{ matrix.os }} strategy: fail-fast: false matrix: os: - ubuntu-latest node-version: - 14.x - 16.x - 18.x - 20.x runs-on: ${{matrix.os}} steps: - uses: actions/checkout@v2 - name: use node ${{ matrix.node-version }} uses: actions/setup-node@v1 with: cache: 'npm' node-version: ${{ matrix.node-version }} - name: install dependencies run: npm install - name: test run: make test env: TEST_SKIP_IP_V6: true
What changed
- Run on Latchkey managed runners with one line (
runs-on), which apply the fixes below automatically and self-heal transient failures. This example useslatchkey-small; pick the runner size that fits the job. - 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.
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 2 jobs (5 with the matrix expanded) per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.