On 01/03/2019 09.22, David Hildenbrand wrote: > On 01.03.19 07:39, Thomas Huth wrote: >> When changing common code of the kvm-unit-tests, one should make sure that >> the tests still compile fine for all target architectures afterwards. But >> compiling kvm-unit-tests for all target architectures manually is cumbersome. >> For people like me who store their git trees on GitLab, this can be done >> automatically via a CI system instead. Using the .gitlab-ci.yml file, auto- >> matic builds are now triggered on each push to a kvm-unit-test repository on >> gitlab.com. Additionally, the script also runs the tests that can be executed >> with QEMU TCG (except for s390x, since the QEMU package of the CI container >> currently does not provide the required s390-ccw bios here). > > Just wondering, doesn't one have to specify a container environment to > use? Is that done in some other configuration? That's for other CI environments (like Travis). For the default on gitlab.com, it's fixed AFAIK. You can provide your own runner scripts, too, but then you also need a dedicated machines where it runs. At least that's how I understood it - I'm also not an expert here. > Or does it always default to some ubuntu/debian thingy? Yes. Not sure whether it's Debian or Ubuntu and which version, though. Thomas
