From 58dbad789d5fa0dc0283e16f1f6944210820d40b Mon Sep 17 00:00:00 2001 From: Jon Mason Date: Thu, 15 Dec 2022 10:24:15 -0500 Subject: [PATCH] CI: define DEFAULT_TAG and CPU_REQUEST DEFAULT_TAG and CPU_REQUEST are being used to help with internal Gitlab pipeline setups know which type of machines to run on, but has no value outside of Arm Corp. Gitlab CI allows for variables to be overridden by default. So, we can give it a default value of NULL/empty and have everything work internally and externally by default. Signed-off-by: Jon Mason --- .gitlab-ci.yml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index e411065e..0a03a1ea 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -1,8 +1,10 @@ image: ghcr.io/siemens/kas/kas:latest-release -# These are needed as the k8s executor doesn't respect the container entrypoint -# by default variables: + CPU_REQUEST: "" + DEFAULT_TAG: "" + # These are needed as the k8s executor doesn't respect the container entrypoint + # by default FF_USE_LEGACY_KUBERNETES_EXECUTION_STRATEGY: 0 FF_KUBERNETES_HONOR_ENTRYPOINT: 1