yocto-build-env: remove no cache argument

Secure boots builds used to end up with a mismatch between the kernel and modules signatures because of the use of cache - to avoid this we temporarily forced builds without cache. With the fix in meta-balena 389054e84c0b1fd382d737c39fb2bb02c2b3e9b2, kernel modules are always set not to use cache and this problem should no longer happen. At least during the i.MX secure boot local builds with cache never hit the problem. Remove the setting not to use cache. Change-type: revert to building secure boot with cache Signed-off-by: Alex Gonzalez <[email protected]>
balena-os · Dec 20, 2024 · a474cae · a474cae
1 parent 3e7a961
commit a474cae
Showing 1 changed file with 0 additions and 1 deletion.
diff --git a/.github/workflows/yocto-build-deploy.yml b/.github/workflows/yocto-build-deploy.yml
@@ -464,7 +464,6 @@ jobs:
           BARYS_ARGUMENTS_VAR="${BARYS_ARGUMENTS_VAR} -a SIGN_GRUB_KEY_ID=${SIGN_GRUB_KEY_ID}"
           BARYS_ARGUMENTS_VAR="${BARYS_ARGUMENTS_VAR} -a SIGN_KMOD_KEY_APPEND=${SIGN_KMOD_KEY_APPEND}"
           BARYS_ARGUMENTS_VAR="${BARYS_ARGUMENTS_VAR} -a SIGN_HAB_PKI_ID=${SIGN_HAB_PKI_ID}"
-          BARYS_ARGUMENTS_VAR="${BARYS_ARGUMENTS_VAR} --bitbake-args --no-setscene"
           echo "BARYS_ARGUMENTS_VAR=${BARYS_ARGUMENTS_VAR}" >>"${GITHUB_ENV}"
 
       # FIXME: Remove this when we shut down the NFS server in early 2025