-
Notifications
You must be signed in to change notification settings - Fork 343
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
Add GHA to test changes compatibility with avocado-vt #5233
Comments
Initial action testing a given branch from the current avocado repository against master branch from https://github.com/avocado-framework/avocado-vt References: avocado-framework#5233 Signed-off-by: Ana Guerrero Lopez <[email protected]>
Initial action testing an avocado development branch against the master branch from https://github.com/avocado-framework/avocado-vt References: avocado-framework#5233 Signed-off-by: Ana Guerrero Lopez <[email protected]>
Initial action testing an avocado development branch against the master branch from https://github.com/avocado-framework/avocado-vt References: avocado-framework#5233 Signed-off-by: Ana Guerrero Lopez <[email protected]>
Initial action testing an avocado development branch against the master branch from https://github.com/avocado-framework/avocado-vt References: avocado-framework#5233 Signed-off-by: Ana Guerrero Lopez <[email protected]>
I proposed a PR #5234 with a re-using the ansible deployment playbook.
@ana thanks for coming up with this. The idea of reusing the "deployment checks", AKA ansible playbooks, is great. I tried it out, and worked great. But there's one limitation of GHA (and pretty much every other free CI offering): it lacks KVM support. And, it's very hard to go deep into Avocado-VT, and prove compatibility, without KVM. I've tried to use TCG to run say a So, while this is certainly helpful, the platform limitation is a concern. We may be better served at this point by having a copy (or subset) of the Avocado-VT Cirrus-CI set to manual or allowing them to fail. PS: my dream solution would be to not add anything in the Avocado repository, but allow manual triggers (like GHA allow) on the Avocado-VT repo, pointing at the branch of a given PR. Comments?
Hi @clebergnu Thanks for your comment. Do you mind copying into #5233 ? Or even opening a new issue with your dream solution more detailed (dreaming is free!). And I'll think what we can do. In the meantime, looks like github is considering to offer nested virtualization github/feedback#8305 If we have the possibility to have a self-hosted runner for tests like this one, it would be also another possible solution.
Sure!
The move from GH is interesting, that would be great! Let's keep an eye on it. About the self-hosted runner, it's something to be considered indeed. Let assess the resources availability (especially the maintenance aspects). Thanks for all the info. |
An initial approach for this could be adding a test that will run in a self-hosted runner while github adds support for virtualization. |
Add a new GH Actions that can be run on-demand to test compatibility with avocado-vt
Reference discussion: avocado-framework/avocado-vt#3295
The text was updated successfully, but these errors were encountered: