From 4a84a7619fc5807929f103044b4cd12a0579b20e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20M=C3=BCller?= Date: Wed, 2 Nov 2022 13:34:27 -0700 Subject: [PATCH] ci: Provide KBUILD_OUTPUT to actions asking for it MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit As of https://github.com/libbpf/ci/pull/67 a bunch of actions honor KBUILD_OUTPUT. Doing so will make it possible to separate source code from build artifacts, which in turn may allow us to support incremental kernel compilation in CI down the line. Irrespective of these future changes, actions pertaining the kernel build now ask for an additional input defining where to store or expect build artifacts. Provide it. Signed-off-by: Daniel Müller --- .github/actions/vmtest/action.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/actions/vmtest/action.yml b/.github/actions/vmtest/action.yml index 798501a..d124fbd 100644 --- a/.github/actions/vmtest/action.yml +++ b/.github/actions/vmtest/action.yml @@ -77,11 +77,14 @@ runs: # 4. prepare rootfs - name: prepare rootfs uses: libbpf/ci/prepare-rootfs@master + env: + KBUILD_OUTPUT: '.kernel' with: project-name: 'libbpf' arch: ${{ inputs.arch }} kernel: ${{ inputs.kernel }} kernel-root: '.kernel' + kbuild-output: ${{ env.KBUILD_OUTPUT }} image-output: '/tmp/root.img' # 5. run selftest in QEMU - name: Run selftests