CI runners

Every Codebahn plan includes hosted CI runners. Jobs with runs-on: self-hosted are picked up automatically.

Runner specs

Hosted runners run on Scaleway instances in the EU (Paris, fr-par). The runner image is based on catthehacker/ubuntu:act-24.04, which provides a GitHub Actions-compatible environment with common build tools pre-installed.

Runner resources scale with your plan tier. Higher tiers get more vCPUs, memory, and concurrent job slots.

Minute counting

Minutes are wall-clock time, not CPU time. A job that takes 90 seconds uses 2 minutes (rounded up). Minutes are counted per job. Three parallel jobs running one minute each use three minutes total.

Minute limits

CI minutes are capped per billing period. When you hit the cap, new jobs queue until the next period or until you purchase a top-up.

There is a 30-minute grace window. Jobs already running when you reach the limit are allowed to finish. This prevents builds from being killed mid-execution.

You receive email warnings at 80% and 95% of your minute allocation.

Top-ups

Purchase additional minutes under Settings > Billing. Top-up minutes are added to your pool immediately and persist until used. They do not expire at the end of a billing period.

Bring your own runner

You can register your own runners alongside the hosted ones. Install the runner binary and register it against your Codebahn instance.

Label routing

Use distinct labels for your own runners. Route jobs with runs-on: my-label to your hardware. Jobs using runs-on: self-hosted go to Codebahn’s hosted runners.

Workflow compatibility

Your .github/workflows/ files work without changes. Actions are resolved from GitHub by default, so uses: actions/checkout@v4 works as-is.

For the full workflow syntax reference, see the upstream Actions documentation.