mirror of
https://gitlab.nic.cz/knot/knot-dns.git
synced 2026-03-01 21:11:15 -05:00
|
|
||
|---|---|---|
| .. | ||
| ansible-roles | ||
| centos7 | ||
| centos8 | ||
| debian9 | ||
| debian10 | ||
| fedora32 | ||
| fedora33 | ||
| leap15 | ||
| ubuntu1604 | ||
| ubuntu1804 | ||
| ubuntu2004 | ||
| ubuntu2010 | ||
| .ansible.cfg | ||
| knot-dns-pkgtest.yaml | ||
| README.md | ||
| repos.yaml | ||
| test-distro.sh | ||
Requirements
- ansible
- vagrant
- libvirt (+vagrant-libvirt) / virtualbox
Usage
vagrant up command is configured to trigger ansible provisioning
which configures OBS repository, installs the knot package, creates
a zone and config file, starts the knot.service and attempts to
resolve the entry from created zone file.
By default, the knot-dns-devel repo is used. To test the
knot-dns-latest or knot-dns-testing repo, set it in repos.yaml
(or use the test-distro.sh script which overwrites this file). If
you're running tests in parallel, they all HAVE TO use the same repo.
Run the following command for every distro (aka directory with Vagrantfile):
./test-distro.sh knot-dns-devel debian9
or
./test-distro.sh knot-dns-testing debian9
or
./test-distro.sh knot-dns-latest debian9
At the end of the test, the package version that was tested is printed out. Make sure you're testing what you intended to.