Deploy Frontend workflow (stanford-crfm/helm)
The Deploy Frontend workflow from stanford-crfm/helm, explained and optimized by Latchkey.
CI health: C - fair
Point runs-on at Latchkey and get caching, job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Deploy Frontend workflow from the stanford-crfm/helm repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.
Below, Latchkey shows a faster, safer version produced by its optimization engine.
The workflow
name: Deploy Frontend
on: workflow_dispatch
jobs:
build:
runs-on: ubuntu-latest
# Deploy to only run on pushes to master
# if: github.event_name == 'push' && github.ref == 'refs/heads/main'
if: github.event_name == 'push' && github.ref == 'refs/heads/react_frontend'
environment:
name: github-pages
env:
VITE_HELM_BENCHMARKS_ENDPOINT: ${{ vars.VITE_HELM_BENCHMARKS_ENDPOINT }}
VITE_HELM_BENCHMARKS_SUITE: ${{ vars.VITE_HELM_BENCHMARKS_SUITE }}
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Use Node.js
uses: actions/setup-node@v4
with:
node-version: '18'
- name: Install Yarn
working-directory: ./helm-frontend
run: npm install --global yarn
- name: Install dependencies
working-directory: ./helm-frontend
run: yarn install
- name: Build app
working-directory: ./helm-frontend
run: yarn build
- name: Upload artifact
uses: actions/upload-pages-artifact@v3
with:
path: ./src/helm/benchmark/static_build/
deploy:
runs-on: ubuntu-latest
needs: build
permissions:
pages: write
id-token: write
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v3
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: Deploy Frontend on: workflow_dispatch jobs: build: timeout-minutes: 30 runs-on: latchkey-small # Deploy to only run on pushes to master # if: github.event_name == 'push' && github.ref == 'refs/heads/main' if: github.event_name == 'push' && github.ref == 'refs/heads/react_frontend' environment: name: github-pages env: VITE_HELM_BENCHMARKS_ENDPOINT: ${{ vars.VITE_HELM_BENCHMARKS_ENDPOINT }} VITE_HELM_BENCHMARKS_SUITE: ${{ vars.VITE_HELM_BENCHMARKS_SUITE }} steps: - name: Checkout code uses: actions/checkout@v4 - name: Use Node.js uses: actions/setup-node@v4 with: cache: 'npm' node-version: '18' - name: Install Yarn working-directory: ./helm-frontend run: npm install --global yarn - name: Install dependencies working-directory: ./helm-frontend run: yarn install - name: Build app working-directory: ./helm-frontend run: yarn build - name: Upload artifact uses: actions/upload-pages-artifact@v3 with: path: ./src/helm/benchmark/static_build/ deploy: timeout-minutes: 30 runs-on: latchkey-small needs: build permissions: pages: write id-token: write environment: name: github-pages url: ${{ steps.deployment.outputs.page_url }} steps: - name: Deploy to GitHub Pages id: deployment uses: actions/deploy-pages@v3
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. - 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 per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.