From: <Venkata.Pyla@toshiba-tsip.com>
To: <jan.kiszka@siemens.com>, <cip-dev@lists.cip-project.org>
Cc: <dinesh.kumar@toshiba-tsip.com>, <kazuhiro3.hayashi@toshiba.co.jp>
Subject: RE: [isar-cip-core 4/5] .reproducible-check-ci.yml: Add BBB target
Date: Tue, 12 Sep 2023 06:52:41 +0000 [thread overview]
Message-ID: <OSYPR01MB55422F888CB0CFC373E89496A4F1A@OSYPR01MB5542.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <0d30d88f-ee82-4b56-9453-85a7e1832242@siemens.com>
>-----Original Message-----
>From: Jan Kiszka <jan.kiszka@siemens.com>
>Sent: Tuesday, September 12, 2023 8:39 AM
>To: pyla venkata(ＴＳＩＰ TMIEC ODG Porting) <Venkata.Pyla@toshiba-
>tsip.com>; cip-dev@lists.cip-project.org
>Cc: dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <dinesh.kumar@toshiba-
>tsip.com>; hayashi kazuhiro(林 和宏 ＤＭＥ ○ＤＩＧ□ＭＰＳ○ＭＰ４)
><kazuhiro3.hayashi@toshiba.co.jp>
>Subject: Re: [isar-cip-core 4/5] .reproducible-check-ci.yml: Add BBB target
>
>On 11.09.23 19:01, venkata.pyla@toshiba-tsip.com wrote:
>> From: venkata pyla <venkata.pyla@toshiba-tsip.com>
>>
>
>Which additional aspects of reproducibility does this target test?
It will try to verify additionally beagle bone specific files like MLO, u-boot and dtb files.
>
>Jan
>
>> Signed-off-by: venkata pyla <venkata.pyla@toshiba-tsip.com>
>> ---
>> .reproducible-check-ci.yml | 16 ++++++++++++++++
>> 1 file changed, 16 insertions(+)
>>
>> diff --git a/.reproducible-check-ci.yml b/.reproducible-check-ci.yml
>> index dec28e2..6bcc215 100644
>> --- a/.reproducible-check-ci.yml
>> +++ b/.reproducible-check-ci.yml
>> @@ -87,6 +87,13 @@ build:qemu-arm-repro-build:
>> variables:
>> target: qemu-arm
>>
>> +build:bbb-repro-build:
>> + extends:
>> + - .repro-build
>> + variables:
>> + target: bbb
>> + extension: "none"
>> +
>> # repro build test
>> test:qemu-amd64-repro-test:
>> extends:
>> @@ -111,3 +118,12 @@ test:qemu-arm-repro-test:
>> target: qemu-arm
>> dependencies:
>> - build:qemu-arm-repro-build
>> +
>> +test:bbb-repro-test:
>> + extends:
>> + - .repro-test
>> + variables:
>> + target: bbb
>> + extension: "none"
>> + dependencies:
>> + - build:bbb-repro-build
>
>--
>Siemens AG, Technology
>Linux Expert Center
next prev parent reply other threads:[~2023-09-12 6:52 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 ` [isar-cip-core 1/5] .reproducible-check-ci.yml: Set default values in base job venkata.pyla
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 [this message]
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=OSYPR01MB55422F888CB0CFC373E89496A4F1A@OSYPR01MB5542.jpnprd01.prod.outlook.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.