Skip to content
Signpost
Generally availableInfrastructure

Self-hosted GitHub Actions runners

The supported way to run CI here: autoscaling self-hosted runners with access to internal networks, artifact caching and deployment credentials.

Lifecycle

No dates planned beyond today.

  1. Proposeda year ago
  2. In development11 months ago
  3. Rolling out8 months ago
  4. Generally available (current stage)4 months ago

Detail

What this is

Autoscaling runners on our own infrastructure, so CI jobs can reach internal services and registries that the hosted runners cannot. Capacity scales with demand and is billed back to the owning team.

Who this affects

Every team running CI. If you are already on GitHub Actions, you get these runners by adding a label to your workflow. If you are still on Jenkins, see Jenkins pipelines for the retirement date.

Updates

Info

Runners are generally available and are now the default for new repositories

Capacity has been stable through three months of rollout. New repositories created from the golden path templates get runner access automatically.

Action required

Start migrating your pipelines — Jenkins switches off in March 2027

Migration is self-service and most pipelines take under a day. Book time with us in #devops if yours is unusual.