ci: add build test targets

In order to unify a github actions per *any* workflow, add a proof
of concept implementation to allow target CI trees to recognize the
required steps they need for 1) build and 2) test) so we can just
use a runner to issue these commands regardless of what tree we are
using:

make ci-build-test
make ci-test

If you have a repo which has a respective target CI set up then
you can just run 'make help' and it will list the commands for each.
For example if you use the linux-modules-kpd tree with something
like this:

make    LINUX_TREE=https://github.com/linux-kdevops/linux-modules-kpd \
	LINUX_TREE_REF=968c2b7cdd6375df4ad08166536a376f64560aa5 \
	defconfig-linux-modules-kpd

make help
...
kdevops built-in CI build tests for linux-modules-kpd:
ci-build-test - Git clones a linux git tree, build Linux, installs and reboots into it
	make selftests

kdevops built-in run time tests for linux-modules-kpd:
ci-test       - Git clones a linux git tree, build Linux, installs and reboots into it
	make selftests-baseline

If your configured tree has none of these files this target is not
allowed. So this is a no-op for trees used which don't have a CI yet
setup.

Signed-off-by: Luis Chamberlain <[email protected]>

Author: mcgrof

.ci/build-test/linux-modules-kpd

@@ -0,0 +1 @@
+make selftests

.ci/test/linux-modules-kpd

@@ -0,0 +1 @@
+make selftests-baseline

Makefile

@@ -235,6 +235,7 @@ $(KDEVOPS_NODES) $(KDEVOPS_VAGRANT): .config $(KDEVOPS_NODES_TEMPLATE)
 DEFAULT_DEPS += $(LOCALHOST_SETUP_WORK)
 
 include scripts/tests.Makefile
+include scripts/ci.Makefile
 
 PHONY += clean
 clean:

scripts/ci.Makefile

@@ -0,0 +1,52 @@
+# SPDX-License-Identifier: copyleft-next-0.3.1
+
+# Collection of CI build targets per kernel repo
+
+ifeq (y,$(CONFIG_BOOTLINUX))
+BOOTLINUX_BASENAME := $(shell basename $(CONFIG_BOOTLINUX_TREE))
+ifneq ($(wildcard .ci/build-test/$(BOOTLINUX_BASENAME)),)
+ifneq ($(wildcard .ci/test/$(BOOTLINUX_BASENAME)),)
+
+ci-build-test: build-test-$(BOOTLINUX_BASENAME)
+
+PHONY += build-test
+
+ci-build-test-%::
+	@set -e; \
+		while IFS= read -r line || [ -n "$$line" ]; do \
+		echo "Running: $$line"; \
+		$$line; \
+	  done < .ci/build-test/$(BOOTLINUX_BASENAME); \
+
+ci-build-test-help-menu:
+	@echo "kdevops built-in CI build tests for $(BOOTLINUX_BASENAME):"
+	@echo "ci-build-test - Git clones a linux git tree, build Linux, installs and reboots into it"
+	@while IFS= read -r line || [ -n "$$line" ]; do \
+		echo -e "\t$$line"; \
+		done < .ci/build-test/$(BOOTLINUX_BASENAME)
+	@echo
+
+HELP_TARGETS += ci-build-test-help-menu
+
+ci-test: build-test-$(BOOTLINUX_BASENAME)
+
+ci-test-%::
+	@set -e; \
+		while IFS= read -r line || [ -n "$$line" ]; do \
+		echo "Running: $$line"; \
+		$$line; \
+	  done < .ci/test/$(BOOTLINUX_BASENAME); \
+
+ci-test-help-menu:
+	@echo "kdevops built-in run time tests for $(BOOTLINUX_BASENAME):"
+	@echo "ci-test       - Git clones a linux git tree, build Linux, installs and reboots into it"
+	@while IFS= read -r line || [ -n "$$line" ]; do \
+		echo -e "\t$$line"; \
+		done < .ci/test/$(BOOTLINUX_BASENAME)
+	@echo
+
+HELP_TARGETS += ci-test-help-menu
+
+endif # We have ci tests entries
+endif # We have ci build tests entries
+endif # CONFIG_BOOTLINUX