scripts: Temporarily build kernel as part of CI
Updating the kernel to v6.12 has shown up a flaw in the workflow for our binary kernel releases. The CI job that builds the binary kernel in the cloud-hypervisor/linux repository fetches the config from the main branch of the cloud-hypervisor/cloud-hypervisor repository. However the CI job to update the kernel version to use is in the cloud-hypervisor repository. As a workaround - update the kernel config and version in the cloud-hypervisor repository to point to v6.12 and use the ability to build the kernel during the CI run. Once merged to main a new release can be made in the linux respository which will build a binary asset using the new config. After that release the CI jobs on the cloud-hypervisor repository can changed back to using the binary kernel assets. Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
This commit is contained in:
parent
6ddbd60d9d
commit
66da3b9970
1 changed files with 1 additions and 1 deletions
|
|
@ -1,7 +1,7 @@
|
|||
#!/usr/bin/env bash
|
||||
hypervisor="kvm"
|
||||
test_filter=""
|
||||
build_kernel=false
|
||||
build_kernel=true
|
||||
|
||||
# Checkout source code of a GIT repo with specified branch and commit
|
||||
# Args:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue