Ciaran Gultnieks 5667d16498 Merge branch 'buildserver-qemu-kvm' into 'master' ... buildserver running in qemu/kvm to support KVM on KVM jenkins.debian.net runs in QEMU/KVM instances, so in order to run the F-Droid buildserver there, it needs to work inside of a KVM guest. The best way I found to do that is to create QEMU/KVM instances via KVM's "nested" virtualization support. This collection of commits enables using QEMU/KVM as the buildserver when `./makebuildserver` detects that it is running inside of KVM. Otherwise, the old behavior is default: running in VirtualBox. I have run these tests inside of ubuntu/16.04 on bare metal, which uses VirtualBox, and ubuntu/16.04 KVM guest, which uses QEMU/KVM. It'll also run on the Guardian Project jenkins box, which is Debian/jessie. @mvdan @CiaranG @krt See merge request !168		2016-09-23 12:25:12 +00:00
..
.gitignore	buildserver: buildserver/Vagrantfile is configed by .yaml file	2016-07-04 23:54:52 +02:00
config.buildserver.py	Add ndk r11c	2016-08-14 00:59:31 +02:00
gradle	makebs: add gradle 3.1	2016-09-23 07:50:52 +02:00
provision-android-ndk	Add ndk r11c	2016-08-14 00:59:31 +02:00
provision-android-sdk	buildserver: only include latest m2 when provisioning	2016-09-19 16:33:12 +02:00
provision-apt-get-install	buildserver: retry apt-get downloads 20 times	2016-09-19 16:33:12 +02:00
provision-apt-proxy	buildserver: send config to vagrant via YAML file	2016-07-04 23:54:52 +02:00
provision-gradle	buildserver: unpack gradle versions with provisioning shell script	2016-06-15 16:35:00 +02:00
provision-pip	buildserver: make provision scripts output name to log	2016-07-04 23:54:52 +02:00
provision-ubuntu-trusty-paramiko	buildserver: make provision scripts output name to log	2016-07-04 23:54:52 +02:00
setup-env-vars	buildserver: do not set NDK env vars, they are handled by fdroid build	2016-06-21 10:29:56 +02:00
Vagrantfile	buildserver: ensure dirs to mount cache exist in guest VM instance	2016-09-19 16:33:12 +02:00