Check it could be build and run from scratch workflow (vas3k/vas3k.club)

The Check it could be build and run from scratch workflow from vas3k/vas3k.club, explained and optimized by Latchkey.

CI health: A - excellent

Point runs-on at Latchkey and get job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →

Source: vas3k/vas3k.club.github/workflows/check_build_and_run.ymlLicense MITView source

What it does

This is the Check it could be build and run from scratch workflow from the vas3k/vas3k.club 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

workflow (.yml)

name: Check it could be build and run from scratch

on: [pull_request]

concurrency:
  group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }}
  cancel-in-progress: true

permissions:
  contents: read

jobs:
  dockerize:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
      - name: Build and start the docker-compose stack
        run: docker compose up -d --wait --wait-timeout 120
      - name: Check build frontend on container
        run: |
          docker compose exec -T webpack npm run build

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: Check it could be build and run from scratch
 
on: [pull_request]
 
concurrency:
  group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }}
  cancel-in-progress: true
 
permissions:
  contents: read
 
jobs:
  dockerize:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
      - name: Build and start the docker-compose stack
        run: docker compose up -d --wait --wait-timeout 120
      - name: Check build frontend on container
        run: |
          docker compose exec -T webpack npm run build

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.
Add a job timeout so a hung step cannot burn hours of runner time.

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

actions/checkout