From: ross.burton@arm.com
To: meta-arm@lists.yoctoproject.org
Subject: [PATCH 1/2] CI: add explanatory comments to variables
Date: Mon, 29 Jan 2024 18:14:00 +0000 [thread overview]
Message-ID: <20240129181401.2170364-1-ross.burton@arm.com> (raw)
From: Ross Burton <ross.burton@arm.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
---
.gitlab-ci.yml | 17 ++++++++++++-----
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 4c6ce14a..4e4c1283 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -1,16 +1,23 @@
image: ${MIRROR_GHCR}/siemens/kas/kas:4.0
variables:
+ # These are needed as the k8s executor doesn't respect the container
+ # entrypoint by default
+ FF_KUBERNETES_HONOR_ENTRYPOINT: 1
+ FF_USE_LEGACY_KUBERNETES_EXECUTION_STRATEGY: 0
+ # The default value for KUBERNETES_CPU_REQUEST
CPU_REQUEST: ""
+ # The default machine tag for the build jobs
DEFAULT_TAG: ""
+ # The machine tag for the ACS test jobs
+ ACS_TAG: ""
+ # The directory to use as the persistent cache (the root for DL_DIR, SSTATE_DIR, etc)
CACHE_DIR: $CI_BUILDS_DIR/persist
+ # The container mirror to use
MIRROR_GHCR: ghcr.io
- # These are needed as the k8s executor doesn't respect the container entrypoint
- # by default
- FF_KUBERNETES_HONOR_ENTRYPOINT: 1
- FF_USE_LEGACY_KUBERNETES_EXECUTION_STRATEGY: 0
+ # Whether to run the SystemReady ACS tests
ACS_TEST: 0
- ACS_TAG: ""
+ # The list of extra Kas fragments to be used when building
EXTRA_KAS_FILES: ""
stages:
--
2.34.1
next reply other threads:[~2024-01-29 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 18:14 ross.burton [this message]
2024-01-29 18:14 ` [PATCH 2/2] CI: allow the runner to set a NVD API key ross.burton
2024-01-30 11:31 ` [PATCH 1/2] CI: add explanatory comments to variables Jon Mason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240129181401.2170364-1-ross.burton@arm.com \
--to=ross.burton@arm.com \
--cc=meta-arm@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).