build workflow (bojand/ghz)
The build workflow from bojand/ghz, explained and optimized by Latchkey.
CI health: C - fair
Point runs-on at Latchkey and get run de-duplication, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the build workflow from the bojand/ghz 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: build
on:
push:
branches:
- master
paths:
- 'go.mod'
- 'go.sum'
- '*.go'
- '*/*.go'
- '*/*/*.go'
- '*/*/*/*.go'
- '*/*/*/*/*.go'
- '*/*/*/*/*/*.go'
- '*/*/*/*/*/*/*.go'
- '*/*/*/*/*/*/*/*.go'
pull_request:
branches:
- master
paths:
- 'go.mod'
- 'go.sum'
- '*.go'
- '*/*.go'
- '*/*/*.go'
- '*/*/*/*.go'
- '*/*/*/*/*.go'
- '*/*/*/*/*/*.go'
- '*/*/*/*/*/*/*.go'
- '*/*/*/*/*/*/*/*.go'
workflow_dispatch:
jobs:
build:
runs-on: ubuntu-latest
env:
GO111MODULE: on
GOLANGCI_LINT_VERSION: v1.58.0
steps:
- name: Check out code
uses: actions/checkout@v5
- name: Set up Go
uses: actions/setup-go@v6
with:
go-version: 1.23.0
- name: golangci-lint
uses: golangci/golangci-lint-action@v2
with:
version: v1.58.0
- name: Test
run: go test -failfast -race
build_docker_image:
name: Build Docker image from latest tag
runs-on: ubuntu-latest
steps:
- name: Build image
run: docker build https://github.com/bojand/ghz.git
env:
DOCKER_BUILDKIT: '1'
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: build on: push: branches: - master paths: - 'go.mod' - 'go.sum' - '*.go' - '*/*.go' - '*/*/*.go' - '*/*/*/*.go' - '*/*/*/*/*.go' - '*/*/*/*/*/*.go' - '*/*/*/*/*/*/*.go' - '*/*/*/*/*/*/*/*.go' pull_request: branches: - master paths: - 'go.mod' - 'go.sum' - '*.go' - '*/*.go' - '*/*/*.go' - '*/*/*/*.go' - '*/*/*/*/*.go' - '*/*/*/*/*/*.go' - '*/*/*/*/*/*/*.go' - '*/*/*/*/*/*/*/*.go' workflow_dispatch: concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: build: timeout-minutes: 30 runs-on: latchkey-small env: GO111MODULE: on GOLANGCI_LINT_VERSION: v1.58.0 steps: - name: Check out code uses: actions/checkout@v5 - name: Set up Go uses: actions/setup-go@v6 with: go-version: 1.23.0 - name: golangci-lint uses: golangci/golangci-lint-action@v2 with: version: v1.58.0 - name: Test run: go test -failfast -race build_docker_image: timeout-minutes: 30 name: Build Docker image from latest tag runs-on: latchkey-small steps: - name: Build image run: docker build https://github.com/bojand/ghz.git env: DOCKER_BUILDKIT: '1'
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.
1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.
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:
- Container pulls and builds
This workflow runs 2 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.