Community Continuous Integration (CI) for GNU Radio and OpenCPI
summary
A community CI lab provides a stable, lights‑out test center plus a prototype workshop with 20+ Plutos and E310 boards, using OpenCPI heterogeneous unit tests integrated with GitLab CI (commits trigger tests, full builds run on weekends) to measure portability and performance. An ADS‑B GNU Radio receiver is ported into RCC and HDL workers (Q15 data), assemblies/containers created for bitfile builds, valid/ready metadata used for data flow, and deployments run on Pluto and E310 with n310 support in progress.
AI-written summary · about
chapters (13)
- 0:00Start
- 3:00Grcon20 Opencpi Workshops
- 4:57Benefits for Application Developers of a Community Ci Test Training Lab
- 9:25The Open Cpi Component Definition
- 10:01Opencpi Component Specification
- 10:51Worker Description
- 11:55Component Definition
- 12:29Rcc Development
- 14:04Rcc Result Data Type
- 14:52Hdl Development
- 15:11Top Level Design
- 17:59Component Libraries
- 18:13General Sdr Component Library
related talks
10mAutomated testing of GNU Radio builds
37mAutomated Testing and Continuous Integration/Delivery: Lessons Learned
28mContinuous Integration of C/C++ Apps for IoT Devices
35mTest Harness: Continuous Testing on Hardware
28mWhat's new in LibreCores CI?
24mIntro: CNCF CI
01h 01mThe Qt Continuous Integration System
18mSimple KernelCI Labs with Labgrid