Test workflow (SadeghHayeri/GreenTunnel)

The Test workflow from SadeghHayeri/GreenTunnel, explained and optimized by Latchkey.

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: SadeghHayeri/GreenTunnel.github/workflows/test.ymlLicense MITView source

What it does

This is the Test workflow from the SadeghHayeri/GreenTunnel 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: Test
on:
  pull_request:
  push:
    branches:
      - main

jobs:
  hadolint:
    name: Test dockerfile syntax
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: hadolint/hadolint-action@v3.3.0
        with:
          dockerfile: Dockerfile
          ignore: DL3025

  node-test:
    name: Test npm package loads
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
      - run: npm ci
      - run: node -e "import('./src/index.js').then(m => { console.log('OK exports:', Object.keys(m)); process.exit(0); })"

  build:
    name: Build and test docker
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Find an open port
        run: |
          CLIENT_PORT=$(shuf -i 10000-19999 -n 1)
          echo "CLIENT_PORT=${CLIENT_PORT}" >> $GITHUB_ENV

      - name: Build docker image
        run: docker build --no-cache --tag sadeghhayeri/greentunnel:${GITHUB_RUN_ID} .

      - name: Run container
        run: |
          DOCKERCONTAINER=$(docker run -p 127.0.0.1:${CLIENT_PORT}:8000 -d sadeghhayeri/greentunnel:${GITHUB_RUN_ID})
          sleep 5
          echo "DOCKERCONTAINER=${DOCKERCONTAINER}" >> $GITHUB_ENV

      - name: Check container is running
        run: docker ps -f id=${DOCKERCONTAINER}

      - name: Check proxy responds
        run: curl -fIs --proxy http://127.0.0.1:${CLIENT_PORT} https://example.com | grep "200"

      - name: Stop and remove container
        run: docker stop ${DOCKERCONTAINER} && docker rm -fv ${DOCKERCONTAINER}

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: Test
on:
  pull_request:
  push:
    branches:
      - main
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  hadolint:
    timeout-minutes: 30
    name: Test dockerfile syntax
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v4
      - uses: hadolint/hadolint-action@v3.3.0
        with:
          dockerfile: Dockerfile
          ignore: DL3025
 
  node-test:
    timeout-minutes: 30
    name: Test npm package loads
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          cache: 'npm'
          node-version: '20'
      - run: npm ci
      - run: node -e "import('./src/index.js').then(m => { console.log('OK exports:', Object.keys(m)); process.exit(0); })"
 
  build:
    timeout-minutes: 30
    name: Build and test docker
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v4
 
      - name: Find an open port
        run: |
          CLIENT_PORT=$(shuf -i 10000-19999 -n 1)
          echo "CLIENT_PORT=${CLIENT_PORT}" >> $GITHUB_ENV
 
      - name: Build docker image
        run: docker build --no-cache --tag sadeghhayeri/greentunnel:${GITHUB_RUN_ID} .
 
      - name: Run container
        run: |
          DOCKERCONTAINER=$(docker run -p 127.0.0.1:${CLIENT_PORT}:8000 -d sadeghhayeri/greentunnel:${GITHUB_RUN_ID})
          sleep 5
          echo "DOCKERCONTAINER=${DOCKERCONTAINER}" >> $GITHUB_ENV
 
      - name: Check container is running
        run: docker ps -f id=${DOCKERCONTAINER}
 
      - name: Check proxy responds
        run: curl -fIs --proxy http://127.0.0.1:${CLIENT_PORT} https://example.com | grep "200"
 
      - name: Stop and remove container
        run: docker stop ${DOCKERCONTAINER} && docker rm -fv ${DOCKERCONTAINER}

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.
Cancel superseded runs when a branch or PR gets a newer push.
Cache dependency installs on the setup step so they are served from cache.
Add a job timeout so a hung step cannot burn hours of runner time.

1 third-party action is referenced by a movable tag. Pin it 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:

Dependency installs
Container pulls and builds
Network fetches

This workflow runs 3 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

actions/checkout actions/setup-node