Call e2e upgrade test workflow (Project-HAMi/HAMi)

The Call e2e upgrade test workflow from Project-HAMi/HAMi, explained and optimized by Latchkey.

What it does

This is the Call e2e upgrade test workflow from the Project-HAMi/HAMi 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: Call e2e upgrade test

on:
  workflow_call:
    inputs:
      ref:
        required: true
        type: string
permissions: write-all

jobs:
  upgrade-e2e:
    runs-on: ubuntu-latest
    steps:
      - name: e2e upgrade test
        # https://github.com/actions/virtual-environments/issues/709
        run: |
          echo "Need to add e2e upgrade test"

The same workflow, on Latchkey

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

name: Call e2e upgrade test
 
on:
  workflow_call:
    inputs:
      ref:
        required: true
        type: string
permissions: write-all
 
jobs:
  upgrade-e2e:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - name: e2e upgrade test
        # https://github.com/actions/virtual-environments/issues/709
        run: |
          echo "Need to add e2e upgrade test"
 

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 uses latchkey-small; pick the runner size that fits the job.
• Add a job timeout so a hung step cannot burn hours of runner time.

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:

• End-to-end and browser tests

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.