Run Lighthouse CI for desktop and mobile workflow (codecombat/codecombat)

The Run Lighthouse CI for desktop and mobile workflow from codecombat/codecombat, explained and optimized by Latchkey.

What it does

This is the Run Lighthouse CI for desktop and mobile workflow from the codecombat/codecombat 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: Run Lighthouse CI for desktop and mobile
on:
  schedule:
    - cron: '0 3 * * *'
jobs:
  lhci:
    name: Lighthouse CI
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v1
      - name: Use Node.js 16.x
        uses: actions/setup-node@v1
        with:
          node-version: 16.x
      - name: run Lighthouse CI
        run: |
          npm install -g @lhci/cli
          lhci autorun --collect.settings.preset=desktop || echo "LHCI Desktop failed!"
          lhci autorun || echo "LHCI Mobile failed!"

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: Run Lighthouse CI for desktop and mobile
on:
  schedule:
    - cron: '0 3 * * *'
jobs:
  lhci:
    timeout-minutes: 30
    name: Lighthouse CI
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v1
      - name: Use Node.js 16.x
        uses: actions/setup-node@v1
        with:
          cache: 'npm'
          node-version: 16.x
      - name: run Lighthouse CI
        run: |
          npm install -g @lhci/cli
          lhci autorun --collect.settings.preset=desktop || echo "LHCI Desktop failed!"
          lhci autorun || echo "LHCI Mobile failed!"
 

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 uses latchkey-small; pick the runner size that fits the job.
• 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 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