Node CI workflow (blueimp/JavaScript-Load-Image)
The Node CI workflow from blueimp/JavaScript-Load-Image, 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 Node CI workflow from the blueimp/JavaScript-Load-Image 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: Node CI
on: [push, pull_request]
jobs:
lint:
runs-on: ubuntu-latest
strategy:
matrix:
node-version: [14, 16]
steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v2
with:
node-version: ${{ matrix.node-version }}
- run: npm install
- run: npm run lint
unit:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: mocha
run: docker-compose run --rm mocha
- name: docker-compose logs
if: always()
run: docker-compose logs nginx
- name: docker-compose down
if: always()
run: docker-compose down -v
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: Node CI on: [push, pull_request] concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: lint: timeout-minutes: 30 runs-on: latchkey-small strategy: matrix: node-version: [14, 16] steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 with: cache: 'npm' node-version: ${{ matrix.node-version }} - run: npm install - run: npm run lint unit: timeout-minutes: 30 runs-on: latchkey-small steps: - uses: actions/checkout@v2 - name: mocha run: docker-compose run --rm mocha - name: docker-compose logs if: always() run: docker-compose logs nginx - name: docker-compose down if: always() run: docker-compose down -v
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 (3 with the matrix expanded) per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.