History

Lars Karlitski 64713449ce Introduce runners We've been using a generic `osbuild-run`, which sets up the build environment (and works around bugs) for all build roots. It is already getting unwieldy, because it tries to detect the OS for some things it configures. It's also about to cause problems for RHEL, which doesn't currently support a python3 shebang without having /etc around. This patch changes the `build` key in a pipeline to not be a pipeline itself, but an object with `runner` and `pipeline` keys. `pipeline` is the build pipeline, as before. `runner` is the name of the runner to use. Runners are programs in the `runners` subdirectory. Three runners are included in this patch. They're copies of osbuild-run for now (except some additions for rhel82). The idea is that each of them only contains the minimal setup code necessary for an OS, and that we can review what's needed when updating a build root. Also modify the `--build-pipeline` command line switch to accept such a build object (instead of a pipeline) and rename it accordingly, to `--build-env`. Correspondingly, `OSBUILD_TEST_BUILD_PIPELINE` → `OSBUILD_TEST_BUILD_ENV`.		2019-11-25 13:05:22 +01:00
..
pipelines	Introduce runners	2019-11-25 13:05:22 +01:00
stages_tests	Introduce runners	2019-11-25 13:05:22 +01:00
testing-rpms	improve vagrant test and its documentation	2019-07-25 12:46:53 +02:00
.gitignore	introduce testing script	2019-07-09 10:29:48 +02:00
__init__.py	osbuild: add description() methods	2019-08-07 10:01:17 +02:00
osbuildtest.py	Introduce runners	2019-11-25 13:05:22 +01:00
README.md	improve vagrant test and its documentation	2019-07-25 12:46:53 +02:00
test_assemblers.py	test/assembler: verify the bootloader	2019-10-13 12:08:08 +02:00
test_boot.py	tests: introduce stage testing	2019-10-08 21:39:35 +02:00
test_osbuild.py	Introduce runners	2019-11-25 13:05:22 +01:00
test_stageinfo.py	Add STAGE_DESC, STAGE_INFO, and STAGE_OPTS to stages	2019-11-13 21:47:03 +01:00
test_stages.py	tests: introduce stage testing	2019-10-08 21:39:35 +02:00

README.md

Setup

To run the tests in vagrant virtual machine, please follow this tutorial: https://developer.fedoraproject.org/tools/vagrant/vagrant-libvirt.html

(run also sudo systemctl start libvirtd)

Using Vagrant

To start a Vagrant box by hand, run vagrant up in this directory. To stop and remove all volumes run vagrant destroy again in this directory.

Troubleshooting

In case you accidentally deleted .vagrant directory, you can use some of these commands in order to get rid of running instance:

$ virsh list # this should display test_default
$ virsh managedsave-remove test_default
$ virsh undefine test_default
# or using vagrant cli tool
$ vagrant global-status
$ vagrant destroy <id>
$ vagrant global-status --prune