liveBook · Manning

Self-hosted runner

As explained in .NET MAUI in Action

A self-hosted runner is a machine managed by the workflow owner that executes automation jobs connected to a repository or organization.

A self-hosted runner is a machine managed by the workflow owner that executes GitHub Actions jobs connected to a repository or organization. It is especially useful for macOS builds, where GitHub-hosted usage carries a substantial time penalty. section 12.2.3 section 12.4

Choose a self-hosted runner when:

  • A workflow requires a macOS agent, such as an iOS build and signing job. section 12.2.3
  • GitHub-hosted minute limits could make repeated or failed builds expensive; macOS minutes receive a 10× penalty. section 12.2.3
  • You want to avoid those hosted-minute limits, while recognizing that a workflow run still cannot exceed 35 days. section 12.2.3

Selecting the runner for an iOS job

Set the job to run on the linked machine, then check out the code and continue with certificate, provisioning-profile, .NET, MAUI workload, build, and artifact-upload steps. section 12.2.3

How .NET MAUI in Action covers it

How deep it goes
Contrasts hosted-minute economics and shows the runner selection line, but defers complete machine-registration instructions.
Examples
Uses an iOS build job configured with runs-on: self-hosted before installing .NET and MAUI and uploading an artifact.
What it assumes
Assumes familiarity with GitHub Actions workflows, YAML jobs, and steps while treating hosted and self-hosted runner choices comparatively.
What you can do after
Configure GitHub Actions jobs to execute on an owner-managed runner and avoid GitHub-hosted macOS minute penalties.
How it connects
Links GitHub Actions workflows and jobs with macOS agents, iOS signing, and GitHub-hosted runners.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of .NET MAUI in Action. The section links point to the parts of the book it draws on.