The kci command is to the new API & Pipeline what the kci_* tools were for the legacy system. It needs to be clearly designed to ease adoption by the community as a tool for KernelCI core developers but also any member of the kernel ecosystem: kernel developers, test system developers etc. I should help with prototyping features by hand before automating them with services running event loops and also work hand-in-hand with the new web dashboard.
Several aspects need to be considered, in particular: feature set, ease of implementation and maintenance of the code, direct user experience, documentation, accessibility.
Here are some of the topics as part of the preparation work:
The
kci
command is to the new API & Pipeline what thekci_*
tools were for the legacy system. It needs to be clearly designed to ease adoption by the community as a tool for KernelCI core developers but also any member of the kernel ecosystem: kernel developers, test system developers etc. I should help with prototyping features by hand before automating them with services running event loops and also work hand-in-hand with the new web dashboard.Several aspects need to be considered, in particular: feature set, ease of implementation and maintenance of the code, direct user experience, documentation, accessibility.
Here are some of the topics as part of the preparation work:
Based on the outcome of these, here's the list of tasks to complete:
kernelci.legacy
kci
entry point command implemented using chosen frameworkkci user
kci config
kci job
kci node
kci event
kci storage
Some follow-up GitHub issues will be created for additional commands such as
kci view
,kci bisect
,kci email
etc.