FAQ
- Is HiveWorker available now?
- Not generally. It is in early access and the daemon has not been released. These docs describe how it is designed to work.
- Can HiveWorker read my code?
- No. The GitHub App has no permission for code, contents or secrets. A job checks out code inside its VM, straight from GitHub. The full permission list is on the security page.
- Which jobs can run on it?
- Linux arm64 jobs. macOS, Windows and GPU jobs are not supported in the first release.
- Which machines can join a pool?
- Apple Silicon Macs that belong to members of your organization.
- Do I have to move every workflow?
- No. Only jobs whose
runs-onis ahivelabel run on your pool. Change the label back and the job returns to its previous runner. - What happens if a laptop closes in the middle of a job?
- The job is stopped. It shows as failed in GitHub and can be re-run. If the developer only starts using the machine, the job is slowed down and allowed to finish.
- What happens when no machine is free?
- The job waits in GitHub's queue until one is.
- Do I need a credit card to start?
- No. A new organization starts with a trial grant. Putting a card on file doubles it.
- What is the HiveWorker token?
- It is how jobs are paid for. Each job has a price, and prices are shown with a US dollar estimate. See Pricing.
- Can I use it on a personal account?
- Not in the first release. HiveWorker installs on organizations.
- How do I get help or report a problem?
- Write to auth@thecomputerplumbers.com.