| Message ID | 20221020140938.7171-1-jon.mason@arm.com |
|---|---|
| State | New |
| Headers | show |
| Series | CI: Remove host bitbake variables | expand |
On Thu, 20 Oct 2022 10:09:38 -0400, Jon Mason wrote: > Bitbake variables were being set in KAS for the unique Gitlab CI > configuration being used internally. While this should not have been > significantly detrimental for other setups, this shouldn't be necessary > with proper runner setup. Removing them here to all for a more generic > CI experience. Applied, thanks! [1/1] CI: Remove host bitbake variables commit: d3541b1e29667ab386b8b87292e8d9d5760aaa3a Best regards,
diff --git a/ci/base.yml b/ci/base.yml index 3619b8f2..0c211e4a 100644 --- a/ci/base.yml +++ b/ci/base.yml @@ -26,13 +26,7 @@ env: local_conf_header: base: | - BB_SERVER_TIMEOUT = "60" CONF_VERSION = "2" - BB_NUMBER_THREADS = "16" - PARALLEL_MAKE = "-j16" - XZ_MEMLIMIT = "25%" - XZ_THREADS = "16" - ZSTD_THREADS = "16" LICENSE_FLAGS_ACCEPTED += "Arm-FVP-EULA" setup: | PACKAGE_CLASSES = "package_ipk"
Bitbake variables were being set in KAS for the unique Gitlab CI configuration being used internally. While this should not have been significantly detrimental for other setups, this shouldn't be necessary with proper runner setup. Removing them here to all for a more generic CI experience. Signed-off-by: Jon Mason <jon.mason@arm.com> --- ci/base.yml | 6 ------ 1 file changed, 6 deletions(-)