CI tests workflow (moment/moment-timezone)
The CI tests workflow from moment/moment-timezone, explained and optimized by Latchkey.
CI health: C - fair
Point runs-on at Latchkey and get 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 tests workflow from the moment/moment-timezone 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: CI tests
on:
push:
branches:
- master
- develop
- release*
pull_request:
workflow_dispatch:
jobs:
test:
name: Run tests
runs-on: ubuntu-latest
strategy:
matrix:
# Use the latest version of Node.js, plus the 3 most recent LTS lines
node-version:
- latest
- lts/*
- lts/-1
- lts/-2 # Probably EOL depending on release schedules, but still good to test
steps:
- uses: actions/checkout@v4
- name: Use Node.js ${{ matrix.node-version }}
uses: actions/setup-node@v4
with:
node-version: ${{ matrix.node-version }}
cache: npm
- name: Install dependencies
run: npm ci
- name: Run tests
run: npm test
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: CI tests on: push: branches: - master - develop - release* pull_request: workflow_dispatch: concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: test: timeout-minutes: 30 name: Run tests runs-on: latchkey-small strategy: matrix: # Use the latest version of Node.js, plus the 3 most recent LTS lines node-version: - latest - lts/* - lts/-1 - lts/-2 # Probably EOL depending on release schedules, but still good to test steps: - uses: actions/checkout@v4 - name: Use Node.js ${{ matrix.node-version }} uses: actions/setup-node@v4 with: node-version: ${{ matrix.node-version }} cache: npm - name: Install dependencies run: npm ci - name: Run tests run: npm test
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.
- 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 1 job (4 with the matrix expanded) per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.