config: jobs-*: replace KernelCI containers with TuxMake containers #1376
Conversation
Replace the KernelCI build container images with the corresponding TuxMake images. This aligns the build environment with the toolchains and configurations provided by TuxMake and ensures consistent, reproducible kernel builds across architectures. Key improvements over the previous KernelCI containers: - Reproducible, uniform build environments across all architectures - Lower maintenance burden with upstream-maintained images - First-class support for cross-compilers, QEMU, and common kernel toolchains - Stable, versioned interface optimized for CI workflows - Better integration with modern CI systems and cloud-native pipelines No functional changes to the build steps; only the container source is updated. Only dtbs_check affected. Signed-off-by: Alok Ranjan <[email protected]>
|
@nuclearcat Do the KCI containers have any cached content (such as files, configuration fragments, or firmware) before build jobs are processed on them ? |
|
Yes, they include kernelci-core components and configuration fragments, as well as pahole and dtschema. Before we replace the containers, I think we should discuss the process. For example, what happens if we need to change the version of pahole? or add some new dependency to build some of tools in kernel. |
|
Most likely best way will be to build kernelci containers based on this images, similar as we do with debos and existing compiling tools: |
2 participants
Replace the KernelCI build container images with the corresponding TuxMake images. This aligns the build environment with the toolchains and configurations provided by TuxMake and ensures consistent, reproducible kernel builds across architectures.
Key improvements over the previous KernelCI containers:
No functional changes to the build steps; only the container source is updated. Only dtbs_check affected.