01. CI に macOS ノードが必要な理由

iOS/macOS builds, code signing, and uploads depend on Xcode and Apple tooling, and Apple only supports these on macOS. GitHub-hosted macOS runners are billed per minute and can have long queues; self-hosted Macs mean procurement, depreciation, and ops. Teams that need stable, scalable macOS build nodes therefore choose among hosted queues, on-prem Macs, or day-rental physical Macs. Reference data: (1) GitHub offers macOS 26 and Apple Silicon runners (macos-26 / macos-26-xlarge) in 2026, but at higher cost and concurrency limits. (2) Eighteen-month TCO for a single M4 Mac mini used for CI often exceeds day-rental by 35% or more (including capital and ops). (3) A day-rental Mac node can be provisioned and running a first build within about 2 hours.

02. 日払い vs 自社構築 vs ホスト型

Use the table below to compare cost, latency, control, and typical use:

Dimension	GitHub Hosted macOS	Self-Hosted Mac	Day-Rental Mac
Per-build cost	Per-minute billing; queue time can be long	Depreciation, power, labor; high fixed cost	Per-day billing; pay only for days used
Time to first run	Immediate, but concurrency and region limits	Weeks to months for procurement	Typically within 2 hours; start and stop as needed
Control	Fixed images; no long-term cache or custom kernel	Full control; persistent cache and images	Dedicated machine; install tools and cache; close to self-hosted
Best for	Open source, low-frequency builds, tight budget	Long-term high concurrency, strict compliance	Sprint crunch, short projects, elastic scale, try before buy

03. ノード選定（構成・リージョン・レイテンシ）

When day-renting a Mac, choose config (e.g. M4 16GB for small/medium projects, 24GB/32GB for large Swift or parallel jobs), region (e.g. Hong Kong or Singapore; same region as the repo reduces clone latency), and network (access to GitHub/GitLab and Apple services). Pain points: (1) Under-provisioning leads to timeouts or OOM; over-provisioning raises daily cost. (2) Wrong region can double git clone and dependency download time. (3) No cache disk or cleanup wastes time on repeated builds. Start with a mid-tier config (e.g. M4 24GB), measure for 1–2 days, then scale. See Day-Rental Mac FAQ and SSH/VNC and Plans and pricing.

04. レイテンシと安定性

Before committing, run a small test: Cold start — time from job dispatch to first command on the runner; self-hosted Macs are often under 30 seconds. Repo clone — same-region nodes typically keep clone to 1–3 minutes (repo-size dependent). Build time — should match a local Mac of the same spec; 10–20 minutes for a full Xcode build on M4 is normal. For stability, use a day-rent Mac with fixed IP or persistent session to avoid mid-run disconnects; install the runner as a service (e.g. ./svc.sh install) so it survives reboots. Reference data: (1) GitHub recommends a dedicated account and Rosetta 2 on Apple Silicon for x86 dependencies. (2) Jenkins recommends at least 4 vCPU and 8GB RAM for macOS agents; 16GB+ for Xcode. (3) With the node in the same region as GitHub, actions/checkout for a ~10GB repo can stay under 2 minutes.

05. GitHub Actions または Jenkins への5ステップ接続

Five steps from provisioning to first build:

Choose node config and region: Pick M4 16GB/24GB etc. by project size; align region with the repo (e.g. Hong Kong or Singapore for GitHub).
Provision day-rent Mac and get SSH details: From the provider get IP, port, and SSH key or password; see SSH/VNC connection guide.
Install Runner or Jenkins Agent: For GitHub, run the official config script on the Mac and select self-hosted; for Jenkins, add a macOS node under Manage → Nodes and start the agent via SSH. Example (GitHub Actions self-hosted runner as a service):

# Install as service, start on boot
./svc.sh install
./svc.sh start

Configure workflow and secrets: In the GitHub workflow set runs-on: self-hosted or the right label; for signing, add certs and profiles to Secrets and import into Keychain in the job. For Jenkins, set the node label and credentials in the Pipeline.
Verify build and latency: Trigger a full build and record queue → start → finish times; adjust node count and cache strategy accordingly.

06. 他案の限界と日払いMacが選ばれる理由

GitHub-hosted macOS runners are quick to use but suffer from queue time and rising per-build cost at scale, with no deep customization (e.g. long-lived cache, specific Xcode version). Self-hosted Macs require upfront investment and ongoing ops, which is a poor fit for short projects or variable demand. Day-rental physical Macs keep control close to self-hosted while turning fixed cost into per-day spend, ideal for “run for a week during review crunch” or “try for 2 weeks before buying hardware.” Provision in about 2 hours and release when done, with no depreciation or maintenance. If you want stable, low-latency macOS CI/CD without building a lab, day-rental Mac is the best balance of cost and flexibility.

07. CTA

利用を開始するには、日払いプランと料金および SSH/VNC 接続ガイドを参照し、リージョン（香港・シンガポールなど）を選択してください。CI/CD の全体構築については日払いMacガイドをご覧ください。

2026 CI/CD 完全ガイド：日払いMacで
GitHub Actions / Jenkins ノード選定・レイテンシと安定性

目次