1. What's kernelci.org?
  2. Where can I find more info about kernelci.org?
  3. Where can I find the code that kernelci.org is built on?
  4. What is the license used for kernelci.org?
  5. What's a job?
  6. How can I participate in the build test phase?
  7. How can I participate in the boot test phase?
  8. I would like to have my board boot tested, how can I do it?
  9. Can I send you my boards?
  10. How can I contact you?

What's kernelci.org?
kernelci.org, this website, is a build and boot automation tool for upstream Linux kernel trees.
Where can I find more info about kernelci.org?
For more information about kernelci.org and its architecture, please see wiki.kernelci.org.
Where can I find the code that kernelci.org is built on?
The code powering kernelci.org can be found on GitHub: github.com/kernelci/.
There are two main components:
  1. This website
  2. The Kernel CI API
What is the license used for kernelci.org?
kernelci.org, this website and its API, is licensed under the terms of the AGPL v3.0.
kernelci.org relies also on 3-rd party libraries that are licensed under their own terms.
What's a job?
A job is a collection of build and boot data for a given Linux kernel tree/branch.
How can I participate in the build test phase?
If you would like to participate in the build test phase, please contact us.
How can I participate in the boot test phase?
If you would like to boot test your own board, please see the my board section for board requirements. Or, if you would like to help boot test already supported boards please contact us for more information.
I would like to have my board boot tested, how can I do it?
Because the system is in alpha, the best way to participate is to first check your board meets the requirements below. If so, send us your boards, supporting documentation and hardware and we will enable upstream kernel testing on them.

Main requirements for devices to be boot tested by kernelci.org:

  • Must be able to boot a current build and defconfig from a mainline/upstream Linux tree, to a shell prompt. No vendor kernels or out-of-tree patchsets.
  • Have a contact/maintainer who will react to boot failures. We do not want to waste effort adding boards that will never get fixed, and then have to remove them.
  • Ideally, be supported by LAVA v2 for ease of integration.

For more info, please contact us.
Can I send you my boards?
Please see the my board section for board requirements, and then please contact us for more information.
How can I contact you?
If you can't find an answer to your questions in this page, please contact us.