From b27756242ec02cf256b761e4a5e79d3a051700f5 Mon Sep 17 00:00:00 2001 From: Jose Quaresma Date: Mon, 7 Sep 2026 15:05:47 +0100 Subject: [PATCH] ci: use specific variable for build-id The content of BUILD_ID is usually always different each time it's runs or parsed. This happens because the variable contains the value of DATETIME or the ${{ github.run_id }}-${{ github.run_attempt }} github ci action. Therefore, we should rule out running any task again if it is solely due to changes in the BUILD_ID. The variable BUILD_ID should be excluded from the dependencies. To do this more easily, the variable QCOM_BUILD_ID is introduced. Signed-off-by: Jose Quaresma --- .github/workflows/compile.yml | 2 +- ci/base.yml | 4 +++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/.github/workflows/compile.yml b/.github/workflows/compile.yml index 55e9ebe8d..434a2e0e2 100644 --- a/.github/workflows/compile.yml +++ b/.github/workflows/compile.yml @@ -90,7 +90,7 @@ jobs: version: 14 local_conf_header: build-id: | - BUILD_ID = "${BUILD_ID}" + QCOM_BUILD_ID = "${BUILD_ID}" EOF env: INPUTS_CACHE_DIR: ${{inputs.cache_dir}} diff --git a/ci/base.yml b/ci/base.yml index ff38fc737..f967a62aa 100644 --- a/ci/base.yml +++ b/ci/base.yml @@ -69,7 +69,9 @@ local_conf_header: # Use a weak assignment so the CI override wins regardless of how kas # orders the merged local.conf fragments. OS_RELEASE_FIELDS:append = " BUILD_ID" - BUILD_ID ?= "local-${DATETIME}" + QCOM_BUILD_ID ?= "local-${DATETIME}" + BUILD_ID ?= "${QCOM_BUILD_ID}" + BUILD_ID[vardepsexclude] ?= "QCOM_BUILD_ID" machine: unset