From: Sai.Sathujoda@toshiba-tsip.com
To: cip-dev@lists.cip-project.org, jan.kiszka@siemens.com
Cc: Sai Sathujoda <Sai.Sathujoda@toshiba-tsip.com>,
dinesh.kumar@toshiba-tsip.com, kazuhiro3.hayashi@toshiba.co.jp
Subject: [isar-cip-core v2 2/2] .gitlab-ci.yml: Add condition check in .build_base to build v2 image
Date: Wed, 14 Feb 2024 21:03:41 +0530 [thread overview]
Message-ID: <20240214153341.3543690-3-Sai.Sathujoda@toshiba-tsip.com> (raw)
In-Reply-To: <20240214153341.3543690-1-Sai.Sathujoda@toshiba-tsip.com>
From: Sai Sathujoda <Sai.Sathujoda@toshiba-tsip.com>
To re-use the built artifacts of v1 image, the consecutive build must
happen in the project directory of the job. So if use_swu is enabled, then
a consecutive build with a minor recipe change is done to get an .swu
artifact for swupdate testing in LAVA.
Signed-off-by: Sai Sathujoda <Sai.Sathujoda@toshiba-tsip.com>
---
.gitlab-ci.yml | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 4f87ec3..8ce7118 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -25,6 +25,7 @@ variables:
dtb: none
deploy: enable
deploy_kernelci: disable
+ use_swu: disable
stages:
- build
@@ -66,6 +67,12 @@ default:
- echo "Building ${base_yaml}"
- kas build ${base_yaml}
- if [ "${deploy}" = "enable" ]; then scripts/deploy-cip-core.sh ${release} ${target} ${extension} ${dtb} ${CI_COMMIT_REF_SLUG}; fi
+ - >
+ if [ "${use_swu}" = "enable" ]; then
+ echo "PV = \"2.0\"" >> recipes-core/images/cip-core-image-security.bb
+ kas build ${base_yaml}
+ scripts/deploy-cip-core.sh ${release} ${target} ${extension} ${dtb} ${CI_COMMIT_REF_SLUG} ${use_swu}
+ fi
- if [ "${deploy_kernelci}" = "enable" ]; then scripts/deploy-kernelci.py ${release} ${target} ${extension} ${dtb}; fi
# base image
--
2.30.2
next prev parent reply other threads:[~2024-02-14 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 15:33 [isar-cip-core v2 0/2] Upload .swu file and firmware for LAVA testing Sai.Sathujoda
2024-02-14 15:33 ` [isar-cip-core v2 1/2] deploy-cip-core.sh: Upload only .swu file for v2 QEMU security targets Sai.Sathujoda
2024-02-14 15:33 ` Sai.Sathujoda [this message]
2024-02-14 15:43 ` [isar-cip-core v2 2/2] .gitlab-ci.yml: Add condition check in .build_base to build v2 image Sai.Sathujoda
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=20240214153341.3543690-3-Sai.Sathujoda@toshiba-tsip.com \
--to=sai.sathujoda@toshiba-tsip.com \
--cc=cip-dev@lists.cip-project.org \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=jan.kiszka@siemens.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.