This runbook starts with plan selection, then checks the node, connection credentials, toolchain, signing environment, and build artifacts. The goal is not simply to open the machine, but to complete a reproducible, reversible, fully logged real build on a dedicated physical Mac mini.
Singapore
Japan (Tokyo)
South Korea (Seoul)
Hong Kong
U.S. West
Choosing the wrong node or missing repository access usually takes longer to fix than installing the tools. Before ordering, add the information below to the team task ticket; assign an owner, define verification, and document the rollback path.
Confirm that the members responsible for signing and release have the required Developer Program access, and clarify who manages certificates, provisioning profiles, and the team identifier. Never put sensitive authentication data in ordinary chat messages or build logs.
Definition of done The owner can explain the source, validity scope, and renewal process for the signing materials.Check access to the main repository, submodules, private package sources, artifact repositories, and large-file storage one by one. CI machine credentials must be separate from personal credentials and limited to the minimum permissions required for the build.
Definition of done A clean environment can fetch the complete source and dependencies at their locked versions.Infer the Xcode version from the project configuration, target SDK, compiler requirements, and plugin compatibility. If the project has multiple release branches, record the Xcode and command-line tools version for each branch.
Definition of done The version number, rationale, and compatibility verification commands are documented.Choose from Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the U.S. West. Prioritize the network locations of your code source, dependency mirrors, and users—not geographic distance alone.
Definition of done The target node has been tested from the main office networks, with the network context recorded.Measure peak usage across source code, dependency caches, DerivedData, archives, simulators, and logs. 256GB suits a controlled working set; large assets, multiple toolchain versions, or long-lived caches may require the 2TB configuration or an added storage option.
Definition of done The peak estimate includes temporary build files and reserves space for cleanup and exports.Choose a daily, weekly, monthly, or quarterly term for one-off troubleshooting, iteration sprints, continuous integration, or long-running experiments. Include setup, validation, and final data export time—not just compilation time.
Definition of done The end time, renewal checkpoint, and export owner are defined.Before confirming an order, do not look only at the starting price. First confirm that the resources cover the peak working set, then verify the network route, and finally check every USD amount and optional add-on.
Suitable for standard Xcode builds, automated testing, and light-to-moderate cache sizes.
Suitable for large projects, parallel testing, AI experiments, and workloads with larger resident working sets.
Choose one of the two tiers based on peak memory, disk working set, and the number of parallel tasks.
Choose one node from Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the U.S. West.
Choose daily, weekly, monthly, or quarterly, and ensure the end time covers environment validation and data export.
Check the base model, node, term, and add-ons, confirm the final USD bill, and submit the order.
Only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) are supported. All orders are billed in USD. Actual gateway availability is determined by the backend response.
After receiving the connection details, limit the first session to identity verification, credential updates, and a minimal connection test. If the host fingerprint does not match, stop connecting and verify it through a console support ticket; do not bypass the warning.
From the console order details, read the device ID, host address, port, username, and host fingerprint. Obtain these details only from the current order.
The fingerprint shown on the first SSH connection must match the order details. Record the result in the internal runbook to distinguish expected changes from anomalous connections later.
Change the temporary credentials immediately after the first login. Store them using the team-approved key-management method and confirm that the old credentials are no longer used for routine access.
Run SSH command and file read/write tests first, then check the macOS graphical interface connection if required by the project. Follow the support guide step by step to check the connection method and port.
ssh -p <port> <user>@<host>
uname -m
sw_vers
df -h /
xcode-select -pPrepare the device ID, occurrence time and time zone, network provider, host-fingerprint comparison, reproduction steps, redacted logs, and troubleshooting actions already completed. Do not submit account passwords, wallet private keys, or full card numbers.
Open a console support ticketDo not move everything at once and troubleshoot afterward. Define inputs, verification points, and rollback actions for each path; proceed only after each path passes, so network, dependency, and signing issues do not become mixed together.
Migrate only the datasets required for the build. Avoid copying local caches, old archives, and unknown state into the new environment.
Rebuild the environment from a version manifest instead of copying the entire local system state. Install required tools first, then restore project dependencies and caches layer by layer.
Connect a single test branch to the runner first. After confirming isolation, caching, and log delivery, switch production jobs to the cloud Mac.
Expand branch coverage or task concurrency only after data checksums match, toolchain versions are reproducible, and CI builds are stable. During migration, do not change dependency versions, signing strategy, and scheduling method at the same time.
Installation is not acceptance. After each configuration layer, record the resulting version, path, or permission so the next engineer can reproduce it from the same checklist.
Install the project-specified version and confirm the active developer directory, SDK list, and compiler version. When multiple versions coexist, put the switching command in the runbook.
Set the commit identity, host verification, and least-privilege credentials. Then fetch the main repository, submodules, and large-file objects, and check the default branch and remote URL.
Import the required materials according to the team process, and check access controls and build-process read permissions. Sensitive content must not enter source code, ordinary logs, or shared caches.
Restore dependencies from the lockfiles, distinguishing reusable caches from project state that must be regenerated. Cache keys should include toolchain and dependency versions.
Set separate paths for source, DerivedData, archives, logs, and exported artifacts, and define cleanup and export rules for the end of a task.
The output below can serve as the baseline for the first build. Add or remove commands according to the package managers actually used by the project; never write secrets or complete environment variables to logs.
sw_vers
uname -m
xcodebuild -version
xcode-select -p
git --version
ruby --version
node --version
df -h /A successful compile alone is not enough. First-run acceptance should cover dependency restoration, tests, archiving, signing checks, and artifact download, with duration, exit code, and log location tied to the same commit.
| Order | Check | Execution | Pass criteria | Record |
|---|---|---|---|---|
| 01 | Dependency restoration | Resolve and download all dependencies from the lockfiles, checking private sources, submodules, and cache hits. | No unlocked-version drift; dependency resolution completes; key package versions match the local baseline. | Lockfile checksum, restoration time, cache key, and failed-retry count. |
| 02 | Automated tests | Run the project’s unit tests, integration tests, and required simulator tests. | The exit code is as expected, failed cases have clear ownership, and test result files can be downloaded. | Test target, passed count, failed count, and test-log path. |
| 03 | Archive | Run Archive with the release configuration and confirm the destination, Scheme, SDK, and build settings. | The archive directory is complete; the build and commit numbers are traceable; the warning count is recorded. | Archive duration, Xcode version, commit, and archive checksum. |
| 04 | Signing check | Verify the signing identity, team identifier, provisioning profile, Entitlements, and target bundle identifier. | The signing chain matches the project requirements, and sensitive materials do not appear in public logs or artifact directories. | Check result, exceptions, owner, and verification-command output. |
| 05 | Artifact download | Export the expected artifacts to the acceptance location and check file size, checksum, and extraction results. | Artifacts download completely, checksums match, and naming and retention follow team standards. | Filename, size, checksum, download duration, and storage location. |
Run after clearing regenerable caches to measure full dependency restoration and compilation time. Record disk space before and after to avoid mistaking insufficient space for a compilation issue.
Run again without changing the code to confirm that the cache key works and incorrect artifacts are not reused. Both builds must use the same commit and toolchain version.
Keep one controlled failure in the log format to confirm that CI captures the exit code, key error, test results, and artifact state—not just what is visible in an interactive session.
A cloud Mac can run normally 365 days a year, but long-running tasks still require disk, cache, credential, upgrade-validation, and pre-order-end export procedures. Put these checks in the daily runbook instead of relying on memory.
Monitor source, DerivedData, archives, caches, and log directories separately. Alert thresholds should account for both remaining capacity and growth rate, and recipients must be able to clean up or export data.
Recommended records Total capacity, available capacity, daily growth, and maximum single-archive size.Clean caches by project, toolchain version, and last-used time. Keep lockfiles and cache-key records so you can verify that a re-download after cleanup is expected.
Recommended records Cache path, retention period, cleanup command, result, and space released.Use least-privilege credentials separately for repositories, artifact sources, and CI, and record expiration dates and owners. After rotation, verify that old credentials are invalid and new ones cover only required resources.
Recommended records Credential purpose, permission scope, expiration date, rotation owner, and verification result.Before upgrading, validate Xcode, command-line tools, signing, dependencies, and rollback materials on non-critical tasks. VMDebug does not set scheduled downtime; users schedule upgrades around their own workloads.
Recommended records Pre-upgrade version, target version, compatibility result, rollback materials, and execution time.Keep the last usable task definition, toolchain manifest, and key artifact checksums. If a change fails, stop new tasks first, restore the verified configuration, and retain the failure logs.
Recommended records Trigger condition, pause method, restored version, verification command, and owner.Before the order ends, export and verify code, keys, archives, logs, and required caches. Check checksums after downloading, then remove sensitive content that no longer needs to remain on the device.
Recommended records Export checklist, destination, checksum verification, completion time, and reviewer.Record the exit code and key logs for every build; check disk growth and caches weekly; rotate credentials according to team security policy; validate compatibility before toolchain changes; and reserve ample time for data export before the order ends.
Choose VMDebug M4 or VMDebug M4 Pro, then select a runtime location from Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the U.S. West. Only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) are supported; all orders are billed in USD.