rpm-ostree/tests/vmcheck/sync.sh

#!/bin/bash
set -euo pipefail

. ${commondir}/libvm.sh

set -x
cd ${builddir}
rm insttree -rf
make install DESTDIR=$(pwd)/insttree
ssh -o User=root -F ssh-config vmcheck "ostree admin unlock; cd ~vagrant/sync && rsync -rv insttree/usr/ /usr/ && systemctl restart rpm-ostreed"
Redo `vmcheck` to abstract over ssh-config, drop all building My development environment is now using "pet" docker containers. I use VMs for testing things that require that (like rpm-ostree). This patch builds on work from @jlebon in https://github.com/projectatomic/rpm-ostree/pull/509 to rework `vmcheck` such that it can work on any `ssh-config`. By default we expect this to be Vagrant. However, I go a lot farther and delete the `vmbuild` code that was trying to do builds in a container on the target VM. I think this is still worth pursuing at some point, but for now I think it's reasonable to assume that the rpm-ostree developer audience uses Linux as their host workstation and hence has containers. (There's another important point here in that for developing lower level things like rpm-ostree, there's a strong push to make the VM disposable and not a pet) Closes: #516 Approved by: jlebon 2016-11-14 20:07:43 +03:00			`#!/bin/bash`
			`set -euo pipefail`

			`. ${commondir}/libvm.sh`

			`set -x`
			`cd ${builddir}`
			`rm insttree -rf`
			`make install DESTDIR=$(pwd)/insttree`
			`ssh -o User=root -F ssh-config vmcheck "ostree admin unlock; cd ~vagrant/sync && rsync -rv insttree/usr/ /usr/ && systemctl restart rpm-ostreed"`