Build sgql workflow (zefhub/zef)

The Build sgql workflow from zefhub/zef, explained and optimized by Latchkey.

What it does

This is the Build sgql workflow from the zefhub/zef 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 sgql

on:
  push:
    branches:
      - sgql

jobs:
  build_push:
    runs-on: ubuntu-latest
    steps:
      - name: Check out the repo
        uses: actions/checkout@v3
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v1
      - name: Build
        run: "docker build -f dockerfiles/Dockerfile.sgql -t us-docker.pkg.dev/zefhub-io/sgql/sgql:latest ."
      - name: Push to google
        run: "docker push us-docker.pkg.dev/zefhub-io/sgql/sgql:latest"

The same workflow, on Latchkey

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

name: Build sgql
 
on:
  push:
    branches:
      - sgql
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build_push:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - name: Check out the repo
        uses: actions/checkout@v3
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v1
      - name: Build
        run: "docker build -f dockerfiles/Dockerfile.sgql -t us-docker.pkg.dev/zefhub-io/sgql/sgql:latest ."
      - name: Push to google
        run: "docker push us-docker.pkg.dev/zefhub-io/sgql/sgql:latest"
 

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.
• 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 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