-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows CI #324
Comments
@rbradford I prefer to use the merge queue approach, because we can detect a breaking change for the Windows guest boot before merging to the main branch. I'll create a GHA workflow for the Windows CI. |
retrage
added a commit
to retrage/rust-hypervisor-firmware
that referenced
this issue
Mar 20, 2024
Resolves cloud-hypervisor#324 Signed-off-by: Akira Moroo <[email protected]>
retrage
added a commit
to retrage/rust-hypervisor-firmware
that referenced
this issue
Mar 20, 2024
Resolves cloud-hypervisor#324 Signed-off-by: Akira Moroo <[email protected]>
retrage
added a commit
to retrage/rust-hypervisor-firmware
that referenced
this issue
Mar 20, 2024
Resolves cloud-hypervisor#324 Signed-off-by: Akira Moroo <[email protected]>
retrage
added a commit
to retrage/rust-hypervisor-firmware
that referenced
this issue
Mar 22, 2024
Resolves cloud-hypervisor#324. It also updates the Windows guest image from Windows 2019 to Windows 2022. Signed-off-by: Akira Moroo <[email protected]>
github-merge-queue bot
pushed a commit
that referenced
this issue
Mar 22, 2024
Resolves #324. It also updates the Windows guest image from Windows 2019 to Windows 2022. Signed-off-by: Akira Moroo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We can now self hosted runners which gives us enough disk space to re-enable Windows CI (using runner name "garm-jammy-16"). However since a secret needs to be used to download the image and forks do not have access to secrets we need to decide whether to go with merge queue approach (like Cloud Hypervisor) or only test Windows after it has already been pushed to main.
@retrage What would your preference be?
The text was updated successfully, but these errors were encountered: