History

Tom Gundersen 0a9223b6f2 Pipeline: drop the build setter Take this as an argumnet to __init__ in the same way that `base` is. This avoids us having to deal with the case of someone setting a stage before the build, which does not work as the stage id will be wrong. Signed-off-by: Tom Gundersen <teg@jklm.no>		2019-08-13 17:13:13 +02:00
..
integration_tests	Test refactoring	2019-08-13 15:14:58 +02:00
pipelines	Test refactoring	2019-08-13 15:14:58 +02: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
__main__.py	Test refactoring	2019-08-13 15:14:58 +02:00
Makefile	make vagrant-test idempotent	2019-07-25 15:47:53 +02:00
README.md	improve vagrant test and its documentation	2019-07-25 12:46:53 +02:00
test_osbuild.py	Pipeline: drop the build setter	2019-08-13 17:13:13 +02:00
Vagrantfile	make vagrant-test idempotent	2019-07-25 15:47:53 +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