Build And Push workflow (Finb/bark-server)
The Build And Push workflow from Finb/bark-server, 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 And Push workflow from the Finb/bark-server 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 And Push
on:
push:
tags:
- '*'
jobs:
docker:
runs-on: ubuntu-latest
steps:
-
name: Checkout
uses: actions/checkout@v4
-
name: Set up QEMU
uses: docker/setup-qemu-action@v3
-
name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
-
name: Login to DockerHub
uses: docker/login-action@v3
with:
username: ${{ secrets.DOCKERHUB_USERNAME }}
password: ${{ secrets.DOCKERHUB_TOKEN }}
-
name: Login to GitHub Container Registry
uses: docker/login-action@v3
with:
registry: ghcr.io
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
- name: Environment Variable
id: vars
run: echo "::set-output name=build_version::$(git describe --tags)"
-
name: Build and push
id: docker_build
uses: docker/build-push-action@v6
with:
context: .
file: ./deploy/Dockerfile
platforms: |
linux/arm
linux/arm64
linux/amd64
tags: |
finab/bark-server:latest
finab/bark-server:${{ steps.vars.outputs.build_version }}
ghcr.io/finb/bark-server:latest
ghcr.io/finb/bark-server:${{ steps.vars.outputs.build_version }}
push: true
-
name: Image digest
run: echo ${{ steps.docker_build.outputs.digest }}
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Build And Push on: push: tags: - '*' concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: docker: timeout-minutes: 30 runs-on: latchkey-small steps: - name: Checkout uses: actions/checkout@v4 - name: Set up QEMU uses: docker/setup-qemu-action@v3 - name: Set up Docker Buildx uses: docker/setup-buildx-action@v3 - name: Login to DockerHub uses: docker/login-action@v3 with: username: ${{ secrets.DOCKERHUB_USERNAME }} password: ${{ secrets.DOCKERHUB_TOKEN }} - name: Login to GitHub Container Registry uses: docker/login-action@v3 with: registry: ghcr.io username: ${{ github.actor }} password: ${{ secrets.GITHUB_TOKEN }} - name: Environment Variable id: vars run: echo "::set-output name=build_version::$(git describe --tags)" - name: Build and push id: docker_build uses: docker/build-push-action@v6 with: context: . file: ./deploy/Dockerfile platforms: | linux/arm linux/arm64 linux/amd64 tags: | finab/bark-server:latest finab/bark-server:${{ steps.vars.outputs.build_version }} ghcr.io/finb/bark-server:latest ghcr.io/finb/bark-server:${{ steps.vars.outputs.build_version }} push: true - name: Image digest run: echo ${{ steps.docker_build.outputs.digest }}
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.
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:
- 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.