Skip to content
Latchkey

Docker Image CI with Tag workflow (ysde/grafana-backup-tool)

The Docker Image CI with Tag workflow from ysde/grafana-backup-tool, explained and optimized by Latchkey.

C

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.

Grade your own workflow free or run it on Latchkey →
Source: ysde/grafana-backup-tool.github/workflows/docker-image.ymlLicense MITView source

What it does

This is the Docker Image CI with Tag workflow from the ysde/grafana-backup-tool 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: Docker Image CI with Tag

on:
  push:
    tags:
      - '*'

jobs:
  push_to_registry:
    name: Push tagged docker image to dockerhub
    runs-on: ubuntu-latest
    steps:
      - name: Check out the repo
        uses: actions/checkout@v2
      
      - name: Log in to Docker Hub
        uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
        with:
          username: ${{ secrets.DOCKER_USERNAME }}
          password: ${{ secrets.DOCKER_PASSWORD }}

      - name: Extract metadata (tags, labels) for Docker
        id: meta
        uses: docker/metadata-action@v4
        with:
          images: ysde/docker-grafana-backup-tool

      - name: Extract metadata (tags, labels) for Docker (Slim version)
        id: meta_slim
        uses: docker/metadata-action@v4
        with:
          images: ysde/docker-grafana-backup-tool
          flavor: |
            latest=auto
            suffix=-slim,onlatest=true

      - name: Build and push Docker image
        uses: docker/build-push-action@v4
        with:
          push: true
          tags: ${{ steps.meta.outputs.tags }}
          labels: ${{ steps.meta.outputs.labels }}

      - name: Build and push Docker image slim version
        uses: docker/build-push-action@v4
        with:
          file: ./DockerfileSlim
          push: true
          tags: ${{ steps.meta_slim.outputs.tags }}
          labels: ${{ steps.meta_slim.outputs.labels }}

The same workflow, on Latchkey

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

name: Docker Image CI with Tag
 
on:
  push:
    tags:
      - '*'
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  push_to_registry:
    timeout-minutes: 30
    name: Push tagged docker image to dockerhub
    runs-on: latchkey-small
    steps:
      - name: Check out the repo
        uses: actions/checkout@v2
      
      - name: Log in to Docker Hub
        uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
        with:
          username: ${{ secrets.DOCKER_USERNAME }}
          password: ${{ secrets.DOCKER_PASSWORD }}
 
      - name: Extract metadata (tags, labels) for Docker
        id: meta
        uses: docker/metadata-action@v4
        with:
          images: ysde/docker-grafana-backup-tool
 
      - name: Extract metadata (tags, labels) for Docker (Slim version)
        id: meta_slim
        uses: docker/metadata-action@v4
        with:
          images: ysde/docker-grafana-backup-tool
          flavor: |
            latest=auto
            suffix=-slim,onlatest=true
 
      - name: Build and push Docker image
        uses: docker/build-push-action@v4
        with:
          push: true
          tags: ${{ steps.meta.outputs.tags }}
          labels: ${{ steps.meta.outputs.labels }}
 
      - name: Build and push Docker image slim version
        uses: docker/build-push-action@v4
        with:
          file: ./DockerfileSlim
          push: true
          tags: ${{ steps.meta_slim.outputs.tags }}
          labels: ${{ steps.meta_slim.outputs.labels }}
 

What changed

2 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