From: venkata.pyla@toshiba-tsip.com
To: cip-dev@lists.cip-project.org, jan.kiszka@siemens.com
Cc: venkata pyla <venkata.pyla@toshiba-tsip.com>,
dinesh.kumar@toshiba-tsip.com, kazuhiro3.hayashi@toshiba.co.jp
Subject: [isar-cip-core 1/5] .reproducible-check-ci.yml: Set default values in base job
Date: Mon, 11 Sep 2023 19:01:43 +0530 [thread overview]
Message-ID: <20230911133147.3164-2-venkata.pyla@toshiba-tsip.com> (raw)
In-Reply-To: <20230911133147.3164-1-venkata.pyla@toshiba-tsip.com>
From: venkata pyla <venkata.pyla@toshiba-tsip.com>
The 'wic_targz' and 'extension' values will be same for all repro-build
targets so define them in the base job `report-build`
Signed-off-by: venkata pyla <venkata.pyla@toshiba-tsip.com>
---
.reproducible-check-ci.yml | 11 +++--------
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/.reproducible-check-ci.yml b/.reproducible-check-ci.yml
index 5628b1b..75c8cef 100644
--- a/.reproducible-check-ci.yml
+++ b/.reproducible-check-ci.yml
@@ -13,13 +13,14 @@
.repro-build:
variables:
use_rt: disable
- wic_targz: disable
- targz: enable
+ wic_targz: enable
+ targz: disable
deploy: disable
deploy_kernelci: disable
artifact_suffix: ".tar.gz"
base_yaml: "kas-cip.yml:kas/board/${target}.yml"
release: bookworm
+ extension: ebg-swu
stage: build
tags:
- large
@@ -71,24 +72,18 @@ build:qemu-amd64-repro-build:
- .repro-build
variables:
target: qemu-amd64
- extension: ebg-swu
- wic_targz: enable
build:qemu-arm64-repro-build:
extends:
- .repro-build
variables:
target: qemu-arm64
- extension: ebg-swu
- wic_targz: enable
build:qemu-arm-repro-build:
extends:
- .repro-build
variables:
target: qemu-arm
- extension: ebg-swu
- wic_targz: enable
# repro build test
test:qemu-amd64-repro-test:
--
2.20.1
next prev parent reply other threads:[~2023-09-11 13:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 13:31 [isar-cip-core 0/5] Add security and BBB targets in venkata.pyla
2023-09-11 13:31 ` venkata.pyla [this message]
2023-09-11 13:31 ` [isar-cip-core 2/5] .reproducible-check-ci.yml: Enable security target venkata.pyla
2023-09-11 13:31 ` [isar-cip-core 3/5] reproducible-check: Add option to pass extensions of the image venkata.pyla
2023-09-11 13:31 ` [isar-cip-core 4/5] .reproducible-check-ci.yml: Add BBB target venkata.pyla
2023-09-12 3:08 ` Jan Kiszka
2023-09-12 6:52 ` Venkata.Pyla
2023-09-12 7:50 ` Jan Kiszka
2023-09-13 4:07 ` Venkata.Pyla
2023-09-14 5:52 ` Jan Kiszka
2023-09-14 6:14 ` Venkata.Pyla
2023-09-14 6:18 ` Jan Kiszka
2023-09-11 13:31 ` [isar-cip-core 5/5] scripts/repro-tests.sh: Add *wic.p0 image into reproducible tests venkata.pyla
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=20230911133147.3164-2-venkata.pyla@toshiba-tsip.com \
--to=venkata.pyla@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.