Hello everyone,
A heads up!
Work on moving some aspects of the KernelCI configuration into an in-tree (or per-project, if you wish) file called ".kernelci.yaml" has started and is currently in the early design and implementation stage.
This is why we need your feedback to ensure that the feature implementation moves in the right direction and will meet the user's needs.
Please have a look at the following GitHub issue:
https://github.com/kernelci/kernelci-pipeline/issues/1126
The linked issue is where anyone interested in this feature can get involved to discuss implementation details, ask questions, etc. You can, of course, ask questions here, too.
This new feature will eventually pave the way for the introduction of a push model to KernelCI, along with the pull model we currently have, allowing for the integration of different Git hosting platforms, such as GitHub, GitLab, etc., where events sent to us from these platforms will trigger an appropriate behaviour on the KernelCI's side.
However, this new functionality will be added as a mid-term deliverable, where the ability to configure KernelCI via the ".kernelci.yaml" file is one of the crucial dependencies.
Please don't hesitate to get involved and provide feedback.
Thank you!
On behalf of the KernelCI maintainers,
Krzysztof