Build workflow (bootstrap-vue/bootstrap-vue)
The Build workflow from bootstrap-vue/bootstrap-vue, explained and optimized by Latchkey.
CI health: D - needs work
Run this on Latchkey for self-healing, caching, and up to 58% lower cost.
Grade your own workflow free or run it on Latchkey →What it does
This is the Build workflow from the bootstrap-vue/bootstrap-vue 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: Build
on:
push:
branches:
- dev
- master
pull_request:
branches:
- dev
- master
permissions:
contents: read
jobs:
build:
runs-on: ${{ matrix.os }}
strategy:
matrix:
os: [ubuntu-latest]
node: [18, 20, 22]
steps:
- name: Clone repository
uses: actions/checkout@v4
- name: Set Node.js version
uses: actions/setup-node@v3
with:
node-version: ${{ matrix.node }}
- name: Get yarn cache directory path
id: yarn-cache-dir-path
run: echo "::set-output name=dir::$(yarn cache dir)"
- name: Cache node_modules
uses: actions/cache@v4
with:
path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
key: ${{ matrix.os }}-node-v${{ matrix.node }}-yarn-${{ hashFiles('**/yarn.lock') }}
restore-keys: |
${{ matrix.os }}-node-v${{ matrix.node }}-yarn-
${{ matrix.os }}-node-v${{ matrix.node }}-
${{ matrix.os }}-
- name: Install dependencies
run: yarn install --check-files --frozen-lockfile --non-interactive
- name: Build
run: yarn run build
- name: BundleWatch
run: yarn run bundlewatch
if: matrix.node == '20'
env:
BUNDLEWATCH_GITHUB_TOKEN: "${{ secrets.BUNDLEWATCH_GITHUB_TOKEN }}"
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: Build on: push: branches: - dev - master pull_request: branches: - dev - master permissions: contents: read concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: build: timeout-minutes: 30 runs-on: ${{ matrix.os }} strategy: matrix: os: [ubuntu-latest] node: [18, 20, 22] steps: - name: Clone repository uses: actions/checkout@v4 - name: Set Node.js version uses: actions/setup-node@v3 with: cache: 'npm' node-version: ${{ matrix.node }} - name: Get yarn cache directory path id: yarn-cache-dir-path run: echo "::set-output name=dir::$(yarn cache dir)" - name: Cache node_modules uses: actions/cache@v4 with: path: ${{ steps.yarn-cache-dir-path.outputs.dir }} key: ${{ matrix.os }}-node-v${{ matrix.node }}-yarn-${{ hashFiles('**/yarn.lock') }} restore-keys: | ${{ matrix.os }}-node-v${{ matrix.node }}-yarn- ${{ matrix.os }}-node-v${{ matrix.node }}- ${{ matrix.os }}- - name: Install dependencies run: yarn install --check-files --frozen-lockfile --non-interactive - name: Build run: yarn run build - name: BundleWatch run: yarn run bundlewatch if: matrix.node == '20' env: BUNDLEWATCH_GITHUB_TOKEN: "${{ secrets.BUNDLEWATCH_GITHUB_TOKEN }}"
What changed
- 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 1 job (3 with the matrix expanded) per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.