tests/lcitool/Makefile.include


LCITOOL_REFRESH = $(SRC_PATH)/tests/lcitool/refresh

lcitool:
	@echo 'Manage build environment manifests'
	@echo
	@echo 'Available targets:'
	@echo
	@echo '    lcitool:             Print this help.'
	@echo '    lcitool-refresh:     Re-generate all build environment manifests.'
	@echo

lcitool-help: lcitool

lcitool-refresh:
	$(call quiet-command, cd $(SRC_PATH) && git submodule update --init tests/lcitool/libvirt-ci)
	$(call quiet-command, $(PYTHON) $(LCITOOL_REFRESH))
tests: integrate lcitool for generating build env manifests This introduces https://gitlab.com/libvirt/libvirt-ci as a git submodule at tests/lcitool/libvirt-ci The 'lcitool' program within this submodule will be used to automatically generate build environment manifests from a definition of requirements in tests/lcitool/projects/qemu.yml It will ultimately be capable of generating - Dockerfiles - Package lists for installation in VMs - Variables for configuring Cirrus CI environments When a new build pre-requisite is needed for QEMU, if this package is not currently known to libvirt-ci, it must first be added to the 'mappings.yml' file in the above git repo. Then the submodule can be updated and the build pre-requisite added to the tests/lcitool/projects/qemu.yml file. Now all the build env manifests can be re-generated using 'make lcitool-refresh' This ensures that when a new build pre-requisite is introduced, it is added to all the different OS containers, VMs and Cirrus CI environments consistently. It also facilitates the addition of containers targetting new distros or updating existing containers to new versions of the same distro, where packages might have been renamed. Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Message-Id: <20211215141949.3512719-8-berrange@redhat.com> Message-Id: <20220105135009.1584676-8-alex.bennee@linaro.org> 2022-01-05 13:49:42 +00:00
			`LCITOOL_REFRESH = $(SRC_PATH)/tests/lcitool/refresh`

			`lcitool:`
			`@echo 'Manage build environment manifests'`
			`@echo`
			`@echo 'Available targets:'`
			`@echo`
			`@echo ' lcitool: Print this help.'`
			`@echo ' lcitool-refresh: Re-generate all build environment manifests.'`
			`@echo`

			`lcitool-help: lcitool`

			`lcitool-refresh:`
tests/lcitool: Allow lcitool-refresh in out-of-tree builds, too When running "make lcitool-refresh" in an out-of-tree build, it currently fails with an error message from git like this: fatal: not a git repository (or any parent up to mount point /) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). Fix it by changing to the source directory first before updating the submodule. Signed-off-by: Thomas Huth <thuth@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org> Message-Id: <20220201085554.85733-1-thuth@redhat.com> Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Message-Id: <20220204204335.1689602-15-alex.bennee@linaro.org> 2022-02-04 20:43:23 +00:00			`$(call quiet-command, cd $(SRC_PATH) && git submodule update --init tests/lcitool/libvirt-ci)`
tests/lcitool: Do not use a hard-coded /usr/bin/python3 as python interpreter When running "make lcitool-refresh", this currently uses the hard-coded /usr/bin/python3 from the script's shebang line for running Python. That's bad, since neither /usr/bin/python3 is guaranteed to exist, nor does it honor the python interpreter that the user might have chosen while running the "configure" script. Thus let's rather use $(PYTHON) in the Makefile, and improve the shebang line in the script in case someone runs this directly. Signed-off-by: Thomas Huth <thuth@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org> Message-Id: <20220329063958.262669-1-thuth@redhat.com> Signed-off-by: Laurent Vivier <laurent@vivier.eu> 2022-03-29 08:39:58 +02:00			`$(call quiet-command, $(PYTHON) $(LCITOOL_REFRESH))`