-
Notifications
You must be signed in to change notification settings - Fork 26
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
CI with basic infrastructure deployment #41
Comments
Seems that GitHub actions don't support hardware virtualization due to the use of Azure on DV2 instances, as discussed on this thread: actions/runner-images#183.
Another interesting thing, but out of topic, is this: https://hub.docker.com/r/ennweb/kvm |
A really interesting trick which I'm trying to use is mentioned in this thread: travis-ci/travis-ci#1839 |
This should depend on #50 and use cloud_init images |
To avoid the creation of each image using Packer, we decided to store the already built images on the cloud and download them from the Travis instance. |
@alegrey91 adding to this, we use those images instead of cloud-init images to ensure also support for all cases like luks setups (that are not always supported in cloud-init instances) |
The pipeline seems to be ready. Today I'll do additional tests and then I think we could merge. |
As already mentioned in another thread (#40), this issue is dedicated to the evaluation of the implementation of a Github action to automate the deployment of basic infrastructure, using the following actions:
A basic infrastructure means the ability to deploy one VM for each OS family supported (depending on the time it needs to do the job).
The text was updated successfully, but these errors were encountered: