Cleanup Build Template workflow (e2b-dev/code-interpreter)

The Cleanup Build Template workflow from e2b-dev/code-interpreter, explained and optimized by Latchkey.

What it does

This is the Cleanup Build Template workflow from the e2b-dev/code-interpreter 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: Cleanup Build Template

on:
  workflow_call:
    secrets:
      E2B_TESTS_ACCESS_TOKEN:
        required: true
    inputs:
      E2B_DOMAIN:
        required: false
        type: string
      E2B_TESTS_TEMPLATE:
        required: true
        type: string

permissions:
  contents: read

jobs:
  cleanup:
    name: Cleanup Build Template
    runs-on: ubuntu-latest
    steps:
      - name: Install E2B CLI
        run: npm install -g @e2b/cli

      - name: Cleanup E2B template
        id: cleanup-template
        run: |
          e2b template delete -y "${{ inputs.E2B_TESTS_TEMPLATE }}"
        env:
          E2B_ACCESS_TOKEN: ${{ secrets.E2B_TESTS_ACCESS_TOKEN }}
          E2B_DOMAIN: ${{ inputs.E2B_DOMAIN }}

The same workflow, on Latchkey

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

name: Cleanup Build Template
 
on:
  workflow_call:
    secrets:
      E2B_TESTS_ACCESS_TOKEN:
        required: true
    inputs:
      E2B_DOMAIN:
        required: false
        type: string
      E2B_TESTS_TEMPLATE:
        required: true
        type: string
 
permissions:
  contents: read
 
jobs:
  cleanup:
    timeout-minutes: 30
    name: Cleanup Build Template
    runs-on: latchkey-small
    steps:
      - name: Install E2B CLI
        run: npm install -g @e2b/cli
 
      - name: Cleanup E2B template
        id: cleanup-template
        run: |
          e2b template delete -y "${{ inputs.E2B_TESTS_TEMPLATE }}"
        env:
          E2B_ACCESS_TOKEN: ${{ secrets.E2B_TESTS_ACCESS_TOKEN }}
          E2B_DOMAIN: ${{ inputs.E2B_DOMAIN }}
 

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:

• Dependency installs

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