Getting Started With New KernelCI CLI Tools for Automating Linux Kernel Testing...
Talkat Open Source Summit Japan + AI_dev: Open Source GenAI & ML Summit + Automotive Linux Summit 2025 · 2025-12-08..12-10·
summary
Command-line tools kci-dev and kci-deploy let users trigger Maestro-orchestrated builds, compare specific commits, retry failed nodes, download build logs and run automated bisects, all via JSON/table/quiet output. The system pulls from the KernelCI dashboard and CADB (700,108 builds in seven days cited), so expect large responses and a current need for caching. Actions require a token; read-only queries do not. Planned features include local-patch builds, better dashboard links, and easier local Maestro deployment.
AI-written summary · about
chapters (13)
- 0:00KernelCI CLI tools intro
- 1:08Why KernelCI CLI tools
- 4:05KernelCI infrastructure scale
- 6:15KernelCI Dev and build-try
- 8:21KernelCI Dev use cases
- 11:42KernelCI Dev architecture
- 13:55Installing KernelCI Dev
- 21:44Live demo of KernelCI Dev
- 26:13Analyzing results with KernelCI Dev
- 28:45KernelCI Dev benefits
- 30:18Future plans for KernelCI Dev
- 33:57KernelCI Dev resources
- 35:43Q&A
related talks
40mKernelCI for Embedded: Enhancing Reliability through Scalable Test Automation
40mOne year into the new KernelCI
33mKernel CI – How Far Can It Go?
37mKernel CI – How Far Can It Go?
32mBootstraping a Local KernelCI
38mQuality Beyond Kernelci.Org in Upstream Linux for TI SoCs
33mMerging an existing framework into KernelCI
34mMerging your Kernel Testing Code into KernelCI