Continuous Integration: Jenkins, libvirt and Real Hardware
summary
Jenkins-based CI-RT uses libvirt plus a libvirt extension for R4D (Remote control For Device-under-test) to manage real hardware for compile, boot and latency regression (smoke) tests for Real-Time Linux. Instead of bespoke Jenkins hardware plugins, the approach extends libvirt to integrate remote power controls and serial-console servers so Jenkins can control physical devices the same way it controls VMs. The talk describes libvirt/R4D internals and shows how this integration is used in the CI-RT test system.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 6:11Virtual machines control
- 15:04Building machines
- 22:28Power tests
- 27:48Project integration
- 31:01Power solution
- 36:09Network wrap-up
related talks
40mAutomated Full System Testing on Hardware with OpenQA
27mJenkins with Ruby on Rails
20mContinuous integration for mobile
41mPlug Real Devices into Your Jenkins Process and Automate Testing
20mHow to Setup Test Infrastructure
31mTest-as-a-Service and XenRT
36mLKFT Remote Labs- 41mPlug Real Devices into Your Jenkins Process and Automate Testing