Move a workflow

What changes, what stays the same, and how to move jobs over safely.

A job moves to RaftRun when its runs-on names a RaftRun label. Steps, actions, secrets, environments, artifacts and the GitHub checks UI all stay the same; GitHub still runs the workflow, RaftRun only provides the machine.

Move one workflow first

  1. Check the limitations

    Windows, macOS, Arm64 and GPU jobs can't move yet, and neither can jobs that need GitHub's preinstalled tools without installing them. The full list is on Limitations.

  2. Change runs-on in one workflow

    Pick a busy workflow with a clear pass or fail, such as tests on pull requests. Match the size to what it uses today: ubuntu-latest on GitHub is 4 vCPU and 16 GB for public repositories and 2 vCPU and 8 GB for private ones.

  3. Compare

    After a day, Analytics shows its durations and failure rate, and suggests a size from the CPU and memory it really used. Then move the next workflow.

Switch with a variable

To move many workflows, or to move back quickly, read the label from a repository or organisation variable. Set RUNNER to raft-ubuntu-24.04 under Settings โ†’ Secrets and variables โ†’ Actions โ†’ Variables on GitHub, and clear it to go back.

.github/workflows/ci.yml
jobs:
  build:
    runs-on: ${{ vars.RUNNER || 'ubuntu-latest' }}

Service containers and container jobs

Both work as they do on GitHub, because every machine has Docker. Service containers start next to the job:

.github/workflows/test.yml
jobs:
  test:
    runs-on: raft-ubuntu-24.04-4
    timeout-minutes: 20
    services:
      postgres:
        image: postgres:17
        env:
          POSTGRES_PASSWORD: postgres
        ports: ["5432:5432"]
    steps:
      - uses: actions/checkout@v4
      - run: make test

A job can run inside a container image too. The cache works from inside it.

.github/workflows/build.yml
jobs:
  build:
    runs-on: raft-ubuntu-24.04
    container: node:22
    steps:
      - uses: actions/checkout@v4
      - run: npm ci && npm run build

Things that behave differently

  • Tools are not preinstalled. Add actions/setup-node, setup-python, setup-go and the like. See what is on the machine.
  • Set timeout-minutes. GitHub stops a job at its timeout and RaftRun deletes the machine at once. Without one, a hung job runs until your workspace's longest job. See Limits and timeouts.
  • No fixed IP addresses. If a deploy target allowlists GitHub's IP ranges, it won't recognise RaftRun machines.
  • The cache is opt-in. Until an admin turns it on, actions/cache uses GitHub's cache as before. See Cache.
  • Jobs queue past your concurrency limit. New workspaces start at 4 jobs at once for their first 30 days on RaftRun's machines.