KernelCI kci-dev: Closing the developer feedback loop
summary
kci-dev brings KernelCI access into developer workflows with concrete features: query and filter the huge dataset (about 7,000 builds in recent days), trigger tests on 100+ boards from your tree or branch, and get JSON output and a simple CLI plus new graphical views and Chromium OS coverage. It is scriptable, aims to become a reusable library, currently needs bisect docs and dashboard performance work, and triggering remote runs requires an auth token; installable via pip install kci-dev.
AI-written summary · about
chapters (6)
- 0:00Introduction to KCI-dev
- 1:07Current CI challenges and data scale
- 2:08Features and capabilities of KCI-dev
- 4:38Missing features and improvements needed
- 6:47Making KCI-dev more maintainer-friendly
- 7:34Q&A session
related talks
36mKernelCI - How Can It Impact Your Future?
27mPlugging into the Red Hat kernel CI ecosystem
38mQuality Beyond Kernelci.Org in Upstream Linux for TI SoCs
23mUnifying Kernel Test Reporting with KernelCI
18mSimple KernelCI Labs with Labgrid
39mQuickly Test Your Kernel with GitLab CI
35mCookies for Kernel Developers
34m7 Ways to Make Kernel Developers Like Cookies
