Skip to content
Latchkey

Publish helm chart and docker images workflow (jupyterhub/binderhub)

The Publish helm chart and docker images workflow from jupyterhub/binderhub, explained and optimized by Latchkey.

F

CI health: F - at risk

Point runs-on at Latchkey and get caching, 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: jupyterhub/binderhub.github/workflows/publish.ymlLicense BSD-3-ClauseView source

What it does

This is the Publish helm chart and docker images workflow from the jupyterhub/binderhub repository, a real project running GitHub Actions. It is shown here with attribution under its BSD-3-Clause license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

workflow (.yml)
name: Publish helm chart and docker images

on:
  pull_request:
    paths-ignore:
      - "**.md"
      - "**.rst"
      - "docs/**"
      - "examples/**"
      - ".github/workflows/**"
      - "!.github/workflows/publish.yml"
  push:
    paths-ignore:
      - "**.md"
      - "**.rst"
      - "docs/**"
      - "examples/**"
      - ".github/workflows/**"
      - "!.github/workflows/publish.yml"
    branches-ignore:
      - "dependabot/**"
      - "pre-commit-ci-update-config"
      - "update-*"
  workflow_dispatch:

jobs:
  # Builds and pushes docker images to quay.io, packages the Helm chart and
  # pushes it to jupyterhub/helm-chart@gh-pages where index.yaml represents the
  # JupyterHub organization Helm chart repository.
  #
  # ref: https://github.com/jupyterhub/helm-chart
  # ref: https://quay.io/organization/jupyterhub
  #
  Publish:
    runs-on: ubuntu-latest
    if: startsWith(github.ref, 'refs/tags/') || (github.ref == 'refs/heads/main')
    steps:
      - uses: actions/checkout@v7
        with:
          # chartpress requires the full history
          fetch-depth: 0

      - uses: actions/setup-python@v6
        with:
          python-version: "3.12"

      - uses: actions/setup-node@v6
        # node required to build wheel
        with:
          node-version: "22"

      - name: Set up QEMU (for docker buildx)
        uses: docker/setup-qemu-action@v4

      - name: Set up Docker Buildx (for chartpress multi-arch builds)
        uses: docker/setup-buildx-action@v4

      - name: Setup helm
        uses: azure/setup-helm@v5
        with:
          version: "v3.16.2"

      - name: Install chart publishing dependencies (chartpress, etc)
        run: |
          pip install --no-cache-dir chartpress>=2.1 pyyaml build

      - name: Build binderhub wheel
        run: python3 -m build --wheel .

      - name: Setup push rights to jupyterhub/helm-chart
        # This was setup by...
        # 1. Generating a private/public key pair:
        #    ssh-keygen -t ed25519 -C "jupyterhub/binderhub" -f /tmp/id_ed25519
        # 2. Registering the private key (/tmp/id_ed25519) as a secret for this
        #    repo:
        #    https://github.com/jupyterhub/binderhub/settings/secrets/actions
        # 3. Registering the public key (/tmp/id_ed25519.pub) as a deploy key
        #    with push rights for the jupyterhub/helm chart repo:
        #    https://github.com/jupyterhub/helm-chart/settings/keys
        #
        run: |
          mkdir -p ~/.ssh
          ssh-keyscan github.com >> ~/.ssh/known_hosts
          echo "${{ secrets.JUPYTERHUB_HELM_CHART_DEPLOY_KEY }}" > ~/.ssh/id_ed25519
          chmod 600 ~/.ssh/id_ed25519

      - name: Setup push rights to Quay.io
        # This was setup by...
        # 1. Creating a [Robot Account](https://quay.io/organization/jupyterhub?tab=robots) in the JupyterHub
        # .  quay.io org
        # 2. Giving it enough permissions to push to the binderhub image
        # 3. Putting the robot account's username and password in GitHub actions environment
        run: |
          docker login -u "${{ secrets.QUAY_USERNAME }}" -p "${{ secrets.QUAY_PASSWORD }}" quay.io
          docker login -u "${{ secrets.DOCKER_USERNAME }}" -p "${{ secrets.DOCKER_PASSWORD }}" docker.io

      - name: Configure a git user
        # Having a user.email and user.name configured with git is required to
        # make commits, which is something chartpress does when publishing.
        # While Travis CI had a dummy user by default, GitHub Actions doesn't
        # and require this explicitly setup.
        run: |
          git config --global user.email "github-actions@example.local"
          git config --global user.name "GitHub Actions user"

      - name: Publish images and chart with chartpress
        env:
          GITHUB_REPOSITORY: "${{ github.repository }}"
        run: |
          ./tools/generate-json-schema.py
          ./ci/publish

  PyPI-testbuild:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
        with:
          # Versioneer requires past tags
          fetch-depth: 0
      - uses: actions/setup-python@v6
        with:
          python-version: "3.12"
      - name: Install pypa/build
        run: python -mpip install build
      - name: Build a sdist, and a binary wheel from the sdist
        run: python -mbuild .
      # ref: https://github.com/actions/upload-artifact#readme
      - uses: actions/upload-artifact@v7
        with:
          name: pypi-dist
          path: "dist/*"
          if-no-files-found: error

The same workflow, on Latchkey

Estimated ~20% faster on cache hits, plus fewer wasted runs and a safer supply chain. Added and changed lines are highlighted.

name: Publish helm chart and docker images
 
on:
  pull_request:
    paths-ignore:
      - "**.md"
      - "**.rst"
      - "docs/**"
      - "examples/**"
      - ".github/workflows/**"
      - "!.github/workflows/publish.yml"
  push:
    paths-ignore:
      - "**.md"
      - "**.rst"
      - "docs/**"
      - "examples/**"
      - ".github/workflows/**"
      - "!.github/workflows/publish.yml"
    branches-ignore:
      - "dependabot/**"
      - "pre-commit-ci-update-config"
      - "update-*"
  workflow_dispatch:
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  # Builds and pushes docker images to quay.io, packages the Helm chart and
  # pushes it to jupyterhub/helm-chart@gh-pages where index.yaml represents the
  # JupyterHub organization Helm chart repository.
  #
  # ref: https://github.com/jupyterhub/helm-chart
  # ref: https://quay.io/organization/jupyterhub
  #
  Publish:
    timeout-minutes: 30
    runs-on: latchkey-small
    if: startsWith(github.ref, 'refs/tags/') || (github.ref == 'refs/heads/main')
    steps:
      - uses: actions/checkout@v7
        with:
          # chartpress requires the full history
          fetch-depth: 0
 
      - uses: actions/setup-python@v6
        with:
          python-version: "3.12"
 
      - uses: actions/setup-node@v6
        # node required to build wheel
        with:
          cache: 'npm'
          node-version: "22"
 
      - name: Set up QEMU (for docker buildx)
        uses: docker/setup-qemu-action@v4
 
      - name: Set up Docker Buildx (for chartpress multi-arch builds)
        uses: docker/setup-buildx-action@v4
 
      - name: Setup helm
        uses: azure/setup-helm@v5
        with:
          version: "v3.16.2"
 
      - name: Install chart publishing dependencies (chartpress, etc)
        run: |
          pip install --no-cache-dir chartpress>=2.1 pyyaml build
 
      - name: Build binderhub wheel
        run: python3 -m build --wheel .
 
      - name: Setup push rights to jupyterhub/helm-chart
        # This was setup by...
        # 1. Generating a private/public key pair:
        #    ssh-keygen -t ed25519 -C "jupyterhub/binderhub" -f /tmp/id_ed25519
        # 2. Registering the private key (/tmp/id_ed25519) as a secret for this
        #    repo:
        #    https://github.com/jupyterhub/binderhub/settings/secrets/actions
        # 3. Registering the public key (/tmp/id_ed25519.pub) as a deploy key
        #    with push rights for the jupyterhub/helm chart repo:
        #    https://github.com/jupyterhub/helm-chart/settings/keys
        #
        run: |
          mkdir -p ~/.ssh
          ssh-keyscan github.com >> ~/.ssh/known_hosts
          echo "${{ secrets.JUPYTERHUB_HELM_CHART_DEPLOY_KEY }}" > ~/.ssh/id_ed25519
          chmod 600 ~/.ssh/id_ed25519
 
      - name: Setup push rights to Quay.io
        # This was setup by...
        # 1. Creating a [Robot Account](https://quay.io/organization/jupyterhub?tab=robots) in the JupyterHub
        # .  quay.io org
        # 2. Giving it enough permissions to push to the binderhub image
        # 3. Putting the robot account's username and password in GitHub actions environment
        run: |
          docker login -u "${{ secrets.QUAY_USERNAME }}" -p "${{ secrets.QUAY_PASSWORD }}" quay.io
          docker login -u "${{ secrets.DOCKER_USERNAME }}" -p "${{ secrets.DOCKER_PASSWORD }}" docker.io
 
      - name: Configure a git user
        # Having a user.email and user.name configured with git is required to
        # make commits, which is something chartpress does when publishing.
        # While Travis CI had a dummy user by default, GitHub Actions doesn't
        # and require this explicitly setup.
        run: |
          git config --global user.email "github-actions@example.local"
          git config --global user.name "GitHub Actions user"
 
      - name: Publish images and chart with chartpress
        env:
          GITHUB_REPOSITORY: "${{ github.repository }}"
        run: |
          ./tools/generate-json-schema.py
          ./ci/publish
 
  PyPI-testbuild:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v7
        with:
          # Versioneer requires past tags
          fetch-depth: 0
      - uses: actions/setup-python@v6
        with:
          python-version: "3.12"
      - name: Install pypa/build
        run: python -mpip install build
      - name: Build a sdist, and a binary wheel from the sdist
        run: python -mbuild .
      # ref: https://github.com/actions/upload-artifact#readme
      - uses: actions/upload-artifact@v7
        with:
          name: pypi-dist
          path: "dist/*"
          if-no-files-found: error
 

What changed

3 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 2 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow