rpm-ostree/tests/vmcheck
Jonathan Lebon 38c8040879 vmcheck: clean before building and adapt to new json
If the dir that was rsync'ed already contains build artifacts, we don't
want those contaminating our build process.

Closes: #336
Approved by: cgwalters
2016-06-20 19:57:37 +00:00
..
atomic-centos-continuous.repo tests: Introduce "vmcheck" 2016-06-07 18:39:46 +00:00
checkout.sh vmcheck: clean before building and adapt to new json 2016-06-20 19:57:37 +00:00
commit_and_deploy.sh Makefile-tests: add toplevel vm* targets 2016-06-15 13:38:34 +00:00
Dockerfile.builder vmcheck: create a new deployment instead 2016-06-15 13:38:34 +00:00
Makefile vmcheck: clean before building and adapt to new json 2016-06-20 19:57:37 +00:00
README.md vmcheck: create a new deployment instead 2016-06-15 13:38:34 +00:00
setup.yml vmcheck: Experiment with the name nxs 2016-06-08 14:26:08 +00:00

Using vmcheck

One time setup:

host$ vagrant up
host$ vagrant ssh
vm$ sudo rpm-ostree rebase centos-atomic-continuous:centos-atomic-host/7/x86_64/devel/continuous
vm$ sudo systemctl reboot

Though rebasing on CAHC is not strictly required, it will allow your code to make use of the most recent builds of projects to which rpm-ostree is tightly coupled, such as ostree and libhif.

If you need to test your code with custom ostree or libhif builds, you have no choice for now other than making your own tree (and yum repo for use by the build container). We're hoping to improve this workflow soon.

To synchronize source code on the host system, use:

vagrant rsync

To build and install into the VM:

host$ vagrant ssh
vm$ cd ~/sync/tests/vmcheck
vm$ make build
vm$ make install

At this point, a new deployment containing the new binaries is ready to be used. All that's left is to reboot:

vm$ sudo systemctl reboot