One year into the new KernelCI
summary
One year after launching the rewritten KernelCI system the project reports concrete gains: improved test stability, automated triage for some regressions, and support for bisection via the command-line tool kci.dev. The stack now uses a central database plus ancillary storage, a scheduler called Maestro, and a public API powering dashboard.kernelci.org; KernelCI owns no hardware and runs on donated labs. New integrations include Hexbot and three Linaro toolsets, and notification subscriptions use a .kci.yml flow.
AI-written summary · about
chapters (6)
- 0:00Introduction and project overview
- 7:26User perspective and toolbox approach
- 13:55Technical architecture and data flow
- 19:19Community engagement and collaboration
- 24:17Future plans and roadmap
- 28:15Q&A session
related talks
40mKernelCI for Embedded: Enhancing Reliability through Scalable Test Automation
40mGetting Started With New KernelCI CLI Tools for Automating Linux Kernel Testing...
36mKernelCI - How Can It Impact Your Future?
33mMerging an existing framework into KernelCI
23mUnifying Kernel Test Reporting with KernelCI
33mKernel CI – How Far Can It Go?
34mMerging your Kernel Testing Code into KernelCI
27mPlugging into the Red Hat kernel CI ecosystem