Skip to content
Latchkey

Build and Push Container Image workflow (robertzaage/GroBro)

The Build and Push Container Image workflow from robertzaage/GroBro, explained and optimized by Latchkey.

B

CI health: B - good

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

Grade your own workflow free or run it on Latchkey →
Source: robertzaage/GroBro.github/workflows/docker-build.ymlLicense MITView source

What it does

This is the Build and Push Container Image workflow from the robertzaage/GroBro 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: Build and Push Container Image

on:
  workflow_run:
    workflows: ["CI"]
    types:
      - completed
    branches: [main]
  release:
    types: [published]

jobs:
  docker:
    runs-on: ubuntu-latest
    if: ${{ github.event.workflow_run.conclusion == 'success' || github.event_name == 'release' }}

    permissions:
      contents: read
      packages: write

    steps:
      - name: Set up QEMU
        uses: docker/setup-qemu-action@v4
        
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v4

      - name: Log in to GitHub Container Registry
        uses: docker/login-action@v4
        with:
          registry: ghcr.io
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}

      - uses: actions/checkout@v6
        with:
          ref: ${{ github.event.workflow_run.head_sha || github.sha }}

      - name: Set image tags
        id: vars
        run: |
          if [[ "${{ github.event_name }}" == "release" ]]; then
            echo "TAGS=ghcr.io/robertzaage/grobro:latest,ghcr.io/robertzaage/grobro:${{ github.event.release.tag_name }}" >> $GITHUB_ENV
          else
            echo "TAGS=ghcr.io/robertzaage/grobro:dev" >> $GITHUB_ENV
          fi

      - name: Build and push to GHCR
        uses: docker/build-push-action@v7
        with:
          platforms: linux/amd64,linux/arm64,linux/arm/v7
          file: ./Dockerfile
          push: true
          tags: ${{ env.TAGS }}
          provenance: false

The same workflow, on Latchkey

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

name: Build and Push Container Image
 
on:
  workflow_run:
    workflows: ["CI"]
    types:
      - completed
    branches: [main]
  release:
    types: [published]
 
jobs:
  docker:
    timeout-minutes: 30
    runs-on: latchkey-small
    if: ${{ github.event.workflow_run.conclusion == 'success' || github.event_name == 'release' }}
 
    permissions:
      contents: read
      packages: write
 
    steps:
      - name: Set up QEMU
        uses: docker/setup-qemu-action@v4
        
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v4
 
      - name: Log in to GitHub Container Registry
        uses: docker/login-action@v4
        with:
          registry: ghcr.io
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}
 
      - uses: actions/checkout@v6
        with:
          ref: ${{ github.event.workflow_run.head_sha || github.sha }}
 
      - name: Set image tags
        id: vars
        run: |
          if [[ "${{ github.event_name }}" == "release" ]]; then
            echo "TAGS=ghcr.io/robertzaage/grobro:latest,ghcr.io/robertzaage/grobro:${{ github.event.release.tag_name }}" >> $GITHUB_ENV
          else
            echo "TAGS=ghcr.io/robertzaage/grobro:dev" >> $GITHUB_ENV
          fi
 
      - name: Build and push to GHCR
        uses: docker/build-push-action@v7
        with:
          platforms: linux/amd64,linux/arm64,linux/arm/v7
          file: ./Dockerfile
          push: true
          tags: ${{ env.TAGS }}
          provenance: false
 

What changed

4 third-party actions are referenced by a movable tag. Pin them 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:

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