Skip to content

Conversation

@kdevops-kpd
Copy link

@kdevops-kpd kdevops-kpd bot commented Apr 24, 2025

Pull request for series with
subject: Build once, test everywhere
version: 1
url: https://patchwork.kernel.org/project/kdevops/list/?series=955766

@kdevops-kpd
Copy link
Author

kdevops-kpd bot commented Apr 24, 2025

Upstream branch: 76b19c2
series: https://patchwork.kernel.org/project/kdevops/list/?series=955766
version: 1

@kdevops-kpd
Copy link
Author

kdevops-kpd bot commented Apr 24, 2025

Upstream branch: 370657c
series: https://patchwork.kernel.org/project/kdevops/list/?series=955766
version: 1

Provision a separate guest/instance for the purpose of building
the Linux kernel under test. It's not used yet.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Currently, for cloud configurations or when 9p is disabled, kdevops
builds the test kernel on each test runner. This is inefficient,
and gets worse as the test matrix for a single kernel version scales
out.

Instead we want to build the test kernel once and make the build
artifacts available for test runners to install. This would be
similar to what KOTD does now, except it does not require setting up
a separate yum repo.

For this experiment, I've created a stripped down version of the
bootlinux role that has only the steps needed to build the kernel on
a target node. It adds some steps to create kernel packages and then
fetch them to the control host.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Add a role that can grab the artifacts in workflows/linux/artifacts
and install them on all guests/instances.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
@kdevops-kpd kdevops-kpd bot force-pushed the series/955766=>main branch from 84a4425 to 8a304f8 Compare April 24, 2025 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants