ci: Use self-hosted runners for CI (esp arm testing)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
GitHub Actions runners can be hard to come by so that many workflows backup (at the time of writing we have 3 running and 6 queued workflows). Can we augment this with self-hosted runners? In order to do this, we'd need to make this setup reproducible, probably with Terraform, as we may have to abandon/reprovision/move these compute resources.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's existing GitHub Actions workflows and the current runner requirements, with particular attention to ARM testing. Define what compute resources and Terraform configuration are needed for a reproducible self-hosted setup. Done means the runners can be provisioned, abandoned, and reprovisioned while supporting the affected CI workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, terraform
- Domain
- ci-cd, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100