flatcar-scripts/ci-automation/vendor-testing
Krzesimir Nowak a0b195f876 ci-automation: Allow using --devcontainer-file option too
I seem to have problems with getting a network connectivity inside
QEMU vm when running the tests in the azure machine. I don't know
what's the cause, but for the dev container tests these problems can
be worked around by using the locally provided dev container
image. Make it possible by specifying QEMU_DEVCONTAINER_FILE in the
environment.
2023-05-30 15:59:37 +02:00
..
aws.sh ci-automation: Use plain AMI image for uploads 2022-10-28 17:21:39 +02:00
azure.sh ci-automation/vendor-testing/azure.sh: Use an array for extra instance types 2022-08-03 16:23:15 +02:00
digitalocean.sh ci-automation: Fix secret file handling 2022-05-06 09:16:23 +02:00
equinix_metal.sh ci-automation/vendor-testing/equinix_metal.sh: Use test framework 2022-05-11 11:39:30 +09:00
gce.sh ci-automation/vendor-testing/gce.sh: Test GVNIC and break retest cycle 2022-05-11 12:07:58 +09:00
openstack.sh ci-automation: add openstack to tested vendors 2022-09-29 11:21:25 +02:00
qemu_uefi.sh ci-automation/vendor-testing: add qemu_uefi 2022-02-24 13:54:58 +01:00
qemu_update.sh run-kola-tests.yaml: use new artifacts, local web server 2023-03-28 10:02:17 +02:00
qemu.sh ci-automation: Allow using --devcontainer-file option too 2023-05-30 15:59:37 +02:00
vmware.sh ci-automation/vendor-testing/vmware.sh: Fix unbound variable use 2022-10-11 15:25:56 +02:00