CI with basic infrastructure deployment about terrible

[alegrey91]

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.
Luckily for us, perhaps, seems that Travis-CI do what we need.
Some examples:

• https://github.com/ankidroid/Anki-Android/blob/master/.travis.yml
• https://github.com/mmcc007/test_emulators/blob/master/.travis.yml

Another interesting thing, but out of topic, is this: https://hub.docker.com/r/ennweb/kvm

[alegrey91]

The pipeline seems to be ready. Today I'll do additional tests and then I think we could merge.

[alegrey91]

A really interesting trick which I'm trying to use is mentioned in this thread: travis-ci/travis-ci#1839
The problem we have is that after adding the travis user to the libvirt group, we should restart the session. Obviously this is impossible in Travis CI. For this reason we are going to use the following command to avoid this problem: sudo -E sudo -u $USER -E bash -c "COMMAND".
@89luca89

[89luca89]

This should depend on #50 and use cloud_init images

[alegrey91]

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.
To do this, I've also found an interesting blog which explains how to do this: https://angelov.ai/post/2020/wget-files-from-gdrive/

[89luca89]

@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)