How to Setup Test Infrastructure
summary
Claim: a unified GitHub Actions pipeline ties emulation and real hardware into a cross‑geo pool with goal of ~100 devices, moving from Jenkins to queued GitHub Actions runners. Implementation uses ESXi hypervisors for VMs, Docker and Ansible for deployment, labgrid as coordinator and Elasticsearch for results. Progress is phase‑driven: queued runners, dynamic runner assignment, a coordinator plus generic runners, then a separate reporter runner, two databases and a self‑hosted plus public dashboard.
AI-written summary · about
chapters (8)
- 0:00Intro
- 2:36Transition goals-Environment.
- 5:12Test Scope
- 6:53Infrastructure technologies
- 8:18Unified Hardware Pool and Automated Testing
- 10:10Single Runner, Limited Hardware Pool
- 12:03Multiple Runners, Expanded Hardware Pool
- 14:52Multiple Runners, Expanded and Managed Hardware Pool
related talks
34mMigrating GitHub Actions with Nested Virtualization to a Cloud Native Ecosystem
43mRewriting an Old CI/CD on GitHub Actions for 280 Contributors?
36mRunning the Runners: How CNCF Powers GitHub Actions at Scale
46mQuality Beyond Testing: Jenkins to GitHub Actions Migration: Optimized Processes & QA
59mIntroduction to GitHub Actions
23mDistributed performance testing at the push of a button
37mAutomated Testing and Continuous Integration/Delivery: Lessons Learned
29m(Ab)using GitHub Actions for building & testing kernels