mirror of
https://github.com/cloud-hypervisor/cloud-hypervisor.git
synced 2025-01-03 03:15:20 +00:00
1c67451333
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> |
||
---|---|---|
.. | ||
gitlint | ||
build-custom-image.sh | ||
ch-trace-visualiser.py | ||
check-image-compatibility.sh | ||
common-aarch64.sh | ||
create-cloud-init.sh | ||
dev_cli.sh | ||
package-consistency-check.py | ||
prepare_vdpa.sh | ||
run_coverage.sh | ||
run_integration_tests_aarch64.sh | ||
run_integration_tests_live_migration.sh | ||
run_integration_tests_rate_limiter.sh | ||
run_integration_tests_sgx.sh | ||
run_integration_tests_vfio.sh | ||
run_integration_tests_windows_aarch64.sh | ||
run_integration_tests_windows_x86_64.sh | ||
run_integration_tests_x86_64.sh | ||
run_metrics.sh | ||
run_openapi_tests.sh | ||
run_unit_tests.sh | ||
sha1sums-aarch64 | ||
sha1sums-x86_64 | ||
test-util.sh | ||
windows-11-iot-enterprise-aarch64.raw.sha1 |