Docker deployment workflow (asreview/asreview)
The Docker deployment workflow from asreview/asreview, 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 Docker deployment workflow from the asreview/asreview 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: Docker deployment
on:
release:
types: [published]
pull_request:
paths:
- "Dockerfile"
- ".github/workflows/docker.yml"
jobs:
docker:
if: ${{ (!github.event.release.prerelease) && (github.event_name != 'pull_request')}}
runs-on: ubuntu-latest
permissions:
contents: read
packages: write
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Set up QEMU
uses: docker/setup-qemu-action@v2
- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v2
- name: Build the image for testing
uses: docker/build-push-action@v4
with:
context: .
load: true
tags: asreview/asreview:test
- name: Test the built image
run: |
docker run asreview/asreview:test -h
- name: Docker meta
id: meta
if: github.event_name != 'pull_request'
uses: docker/metadata-action@v4
with:
images: ghcr.io/asreview/asreview
- name: Login to GitHub registry
if: github.event_name != 'pull_request'
uses: docker/login-action@v2
with:
registry: ghcr.io
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
- name: Build and, if it is not a pull request, push to Docker Hub
uses: docker/build-push-action@v4
with:
context: .
platforms: linux/amd64,linux/arm64
push: ${{ github.event_name != 'pull_request' }}
tags: ${{ steps.meta.outputs.tags }},ghcr.io/asreview/asreview:latest
labels: ${{ steps.meta.outputs.labels }}
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Docker deployment on: release: types: [published] pull_request: paths: - "Dockerfile" - ".github/workflows/docker.yml" concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: docker: timeout-minutes: 30 if: ${{ (!github.event.release.prerelease) && (github.event_name != 'pull_request')}} runs-on: latchkey-small permissions: contents: read packages: write steps: - name: Checkout uses: actions/checkout@v4 - name: Set up QEMU uses: docker/setup-qemu-action@v2 - name: Set up Docker Buildx uses: docker/setup-buildx-action@v2 - name: Build the image for testing uses: docker/build-push-action@v4 with: context: . load: true tags: asreview/asreview:test - name: Test the built image run: | docker run asreview/asreview:test -h - name: Docker meta id: meta if: github.event_name != 'pull_request' uses: docker/metadata-action@v4 with: images: ghcr.io/asreview/asreview - name: Login to GitHub registry if: github.event_name != 'pull_request' uses: docker/login-action@v2 with: registry: ghcr.io username: ${{ github.actor }} password: ${{ secrets.GITHUB_TOKEN }} - name: Build and, if it is not a pull request, push to Docker Hub uses: docker/build-push-action@v4 with: context: . platforms: linux/amd64,linux/arm64 push: ${{ github.event_name != 'pull_request' }} tags: ${{ steps.meta.outputs.tags }},ghcr.io/asreview/asreview:latest labels: ${{ steps.meta.outputs.labels }}
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.
5 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.