rpm-ostree/vagrant/Makefile

all:
	echo "Targets: buildimg build install"

BUILDER_ARGS = sudo /usr/bin/docker run --rm -ti --privileged -v /var/roothome:/root
BUILDER_IMG = rpm-ostree-builder

BUILDER_RUN = $(BUILDER_ARGS) $(BUILDER_IMG)

buildimg:
	sudo docker build -t $(BUILDER_IMG) -f Dockerfile.builder .

build:
	$(BUILDER_RUN) ./autogen.sh --prefix=/usr --libdir=/usr/lib64
	$(BUILDER_RUN) sh -c 'make clean && make -j 4'

install: build
	sudo sh checkout.sh
	$(BUILDER_ARGS) -v /etc:/host/etc \
	                -v /ostree/repo/tmp/vmcheck.ro/usr:/host/usr \
	                $(BUILDER_IMG) sudo make install DESTDIR=/host
	sudo VERSION=$(VERSION) sh commit_and_deploy.sh
tests: Introduce "vmcheck" This is infrastructure that's oriented around Vagrant, we do builds inside the target VM (actually inside a Docker container), but then directly `make install DESTDIR=/host/`. The goal here is to have a convenient workflow for: - dev -> hand testing - dev -> run destructive tests Closes: #303 Approved by: jlebon 2016-06-04 17:48:06 +03:00			`all:`
			`echo "Targets: buildimg build install"`

vagrant: set up ssh for root user From Vagrantfile: It's just easier to have ssh set up as root from the start so that tests don't need to sudo, which can sometimes cause issues. If we need to test any unprivileged things, we can still just sudo back into the vagrant user. Closes: #344 Approved by: cgwalters 2016-06-22 18:51:45 +03:00			`BUILDER_ARGS = sudo /usr/bin/docker run --rm -ti --privileged -v /var/roothome:/root`
vmcheck: create a new deployment instead In order for vmcheck to be useful for testing, we need the machine to be in a "clean" state. That is, sitting on a commit, ready for being manipulated. This is a small step towards this goal. Instead of overwriting the files, we use rofiles-fuse to safely install and create a new deployment. Closes: #321 Approved by: cgwalters 2016-06-14 23:27:14 +03:00			`BUILDER_IMG = rpm-ostree-builder`

			`BUILDER_RUN = $(BUILDER_ARGS) $(BUILDER_IMG)`
tests: Introduce "vmcheck" This is infrastructure that's oriented around Vagrant, we do builds inside the target VM (actually inside a Docker container), but then directly `make install DESTDIR=/host/`. The goal here is to have a convenient workflow for: - dev -> hand testing - dev -> run destructive tests Closes: #303 Approved by: jlebon 2016-06-04 17:48:06 +03:00
vmcheck: create a new deployment instead In order for vmcheck to be useful for testing, we need the machine to be in a "clean" state. That is, sitting on a commit, ready for being manipulated. This is a small step towards this goal. Instead of overwriting the files, we use rofiles-fuse to safely install and create a new deployment. Closes: #321 Approved by: cgwalters 2016-06-14 23:27:14 +03:00			`buildimg:`
			`sudo docker build -t $(BUILDER_IMG) -f Dockerfile.builder .`
tests: Introduce "vmcheck" This is infrastructure that's oriented around Vagrant, we do builds inside the target VM (actually inside a Docker container), but then directly `make install DESTDIR=/host/`. The goal here is to have a convenient workflow for: - dev -> hand testing - dev -> run destructive tests Closes: #303 Approved by: jlebon 2016-06-04 17:48:06 +03:00
			`build:`
Makefile-tests: add toplevel vm* targets The `make vmshell` target makes it even easier to immediately try out your changes in a live running Atomic Host. It will automatically provision the VM, sync your latest changes, build, install in a new deployment onto which the VM is rebooted, and drop you in the shell. Closes: #321 Approved by: cgwalters 2016-06-15 00:12:17 +03:00			`$(BUILDER_RUN) ./autogen.sh --prefix=/usr --libdir=/usr/lib64`
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 22:44:46 +03:00			`$(BUILDER_RUN) sh -c 'make clean && make -j 4'`
tests: Introduce "vmcheck" This is infrastructure that's oriented around Vagrant, we do builds inside the target VM (actually inside a Docker container), but then directly `make install DESTDIR=/host/`. The goal here is to have a convenient workflow for: - dev -> hand testing - dev -> run destructive tests Closes: #303 Approved by: jlebon 2016-06-04 17:48:06 +03:00
			`install: build`
vmcheck: create a new deployment instead In order for vmcheck to be useful for testing, we need the machine to be in a "clean" state. That is, sitting on a commit, ready for being manipulated. This is a small step towards this goal. Instead of overwriting the files, we use rofiles-fuse to safely install and create a new deployment. Closes: #321 Approved by: cgwalters 2016-06-14 23:27:14 +03:00			`sudo sh checkout.sh`
			`$(BUILDER_ARGS) -v /etc:/host/etc \`
			`-v /ostree/repo/tmp/vmcheck.ro/usr:/host/usr \`
			`$(BUILDER_IMG) sudo make install DESTDIR=/host`
Makefile-tests: add toplevel vm* targets The `make vmshell` target makes it even easier to immediately try out your changes in a live running Atomic Host. It will automatically provision the VM, sync your latest changes, build, install in a new deployment onto which the VM is rebooted, and drop you in the shell. Closes: #321 Approved by: cgwalters 2016-06-15 00:12:17 +03:00			`sudo VERSION=$(VERSION) sh commit_and_deploy.sh`