Re: [isar-cip-core][PATCH v2 2/2] Enable CI image build and test support for forky

--lSRfHyARIEp7cY4WKtoL
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi Jan,

On Tue, Jul 28, 2026 at 09:26 PM, Kunijadar Shivanand wrote:

>=20
> On Tue, Jul 28, 2026 at 08:29 AM, Jan Kiszka wrote:
>=20
>> On 28.07.26 10:55, [email protected] wrote:
>>=20
>>> From: Shivanand Kunijadar <[email protected]>
>>>=20
>>> Keep these jobs as scheduled and can be scheduled to run every week
>>> just to monitor and fix if there are any issues.
>>> Also set allow_failure:true for these jobs as forky is not officially
>>> released and there will always be some build & test issues.
>>>=20
>>> It includes SWUpdate, secure boot & RB tests.
>>>=20
>>> Signed-off-by: Shivanand Kunijadar <[email protected]=
m>
>>> ---
>>> .gitlab-ci.yml | 148 +++++++++++++++++++++++++++++++++++++
>>> .reproducible-check-ci.yml | 72 ++++++++++++++++++
>>> 2 files changed, 220 insertions(+)
>>>=20
>>> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
>>> index b53def4..b15c5da 100644
>>> --- a/.gitlab-ci.yml
>>> +++ b/.gitlab-ci.yml
>>> @@ -8,6 +8,7 @@
>>> # Jan Kiszka <[email protected]>
>>> # Quirin Gylstorff <[email protected]>
>>> # Nobuhiro Iwamatsu <[email protected]>
>>> +# Shivanand Kunijadar <[email protected]>
>>> #
>>> # SPDX-License-Identifier: MIT
>>> #
>>> @@ -63,6 +64,7 @@ default:
>>> - if [ "${release}" =3D "bullseye" ]; then
>>> base_yaml=3D"${base_yaml}:kas/opt/bullseye.yml"; fi
>>> - if [ "${release}" =3D "bookworm" ]; then
>>> base_yaml=3D"${base_yaml}:kas/opt/bookworm.yml"; fi
>>> - if [ "${release}" =3D "trixie" ]; then
>>> base_yaml=3D"${base_yaml}:kas/opt/trixie.yml"; fi
>>> + - if [ "${release}" =3D "forky" ]; then
>>> base_yaml=3D"${base_yaml}:kas/opt/forky.yml"; fi
>>> - if [ "${release}" =3D "sid" ]; then
>>> base_yaml=3D"${base_yaml}:kas/opt/sid.yml"; fi
>>> - if [ "${encrypt}" =3D "enable" ]; then
>>> base_yaml=3D"${base_yaml}:kas/opt/encrypt-data.yml"; fi
>>> - if [ "${factory_reset}" =3D "enable" ]; then
>>> base_yaml=3D"${base_yaml}:kas/opt/factory-reset.yml"; fi
>>> @@ -399,6 +401,57 @@ build:qemu-arm-base-sid:
>>> separate_home_partition: enable
>>> deploy: enable
>>>=20
>>> +# forky image builds
>>> +.build_base_forky:
>>> + extends:
>>> + - .build_base
>>> + rules:
>>> + - if: $CI_COMMIT_TAG
>>> + when: never
>>> + - if: '$CI_PIPELINE_SOURCE =3D=3D "schedule" && $CI_RUN_UNSTABLE'
>>=20
>> I meant we should migrate both forky and sid under this one
>> CI_RUN_UNSTABLE variable. Now we would still have two of them and would
>> need to set them both in the pipeline schedule.
>=20
>=20
> My idea was as below,
>=20
>=20
> - The CI variable CI_RUN_UNSTABLE_FORKY is changed to CI_RUN_UNSTABLE,
>=20
>=20
>=20
> however CI_RUN_UNSTABLE_SID is not changed in this patch series, will
>=20
>=20
>=20
> update in a separate patch as it is not related to this series.
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> And it was mentioned in the v2 patch series cover letter, I think you
> would have missed that.
>=20
>=20
>=20
> let me know if required I will change CI_RUN_UNSTABLE_SID to
> CI_RUN_UNSTABLE in this series only.
>=20
>=20
>=20
>=20
>=20
>=20
>=20

Any comments on this? Shall i include the above change in this patch series=
?

please let me know, will send v3 patch series accordingly.

Thanks & Regards

Shivanand K

--lSRfHyARIEp7cY4WKtoL
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<div>Hi Jan,&nbsp;</div>
<div>&nbsp;</div>
<div>On Tue, Jul 28, 2026 at 09:26 PM, Kunijadar Shivanand wrote:</div>
<div>
<blockquote>
<div>On Tue, Jul 28, 2026 at 08:29 AM, Jan Kiszka wrote:</div>
<div>
<blockquote>On 28.07.26 10:55, [email protected] wrote:<=
br />
<blockquote>From: Shivanand Kunijadar &lt;Shivanand.Kunijadar@toshiba-tsip.=
com&gt;<br /><br />Keep these jobs as scheduled and can be scheduled to run=
 every week<br />just to monitor and fix if there are any issues.<br />Also=
 set allow_failure:true for these jobs as forky is not officially<br />rele=
ased and there will always be some build &amp; test issues.<br /><br />It i=
ncludes SWUpdate, secure boot &amp; RB tests.<br /><br />Signed-off-by: Shi=
vanand Kunijadar &lt;[email protected]&gt;<br />---<br /=
>.gitlab-ci.yml | 148 +++++++++++++++++++++++++++++++++++++<br />.reproduci=
ble-check-ci.yml | 72 ++++++++++++++++++<br />2 files changed, 220 insertio=
ns(+)<br /><br />diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml<br />index b5=
3def4..b15c5da 100644<br />--- a/.gitlab-ci.yml<br />+++ b/.gitlab-ci.yml<b=
r />@@ -8,6 +8,7 @@<br /># Jan Kiszka &lt;[email protected]&gt;<br />#=
 Quirin Gylstorff &lt;[email protected]&gt;<br /># Nobuhiro Iwam=
atsu &lt;[email protected]&gt;<br />+# Shivanand Kunijadar &=
lt;[email protected]&gt;<br />#<br /># SPDX-License-Iden=
tifier: MIT<br />#<br />@@ -63,6 +64,7 @@ default:<br />- if [ "${release}"=
 =3D "bullseye" ]; then base_yaml=3D"${base_yaml}:kas/opt/bullseye.yml"; fi=
<br />- if [ "${release}" =3D "bookworm" ]; then base_yaml=3D"${base_yaml}:=
kas/opt/bookworm.yml"; fi<br />- if [ "${release}" =3D "trixie" ]; then bas=
e_yaml=3D"${base_yaml}:kas/opt/trixie.yml"; fi<br />+ - if [ "${release}" =
=3D "forky" ]; then base_yaml=3D"${base_yaml}:kas/opt/forky.yml"; fi<br />-=
 if [ "${release}" =3D "sid" ]; then base_yaml=3D"${base_yaml}:kas/opt/sid.=
yml"; fi<br />- if [ "${encrypt}" =3D "enable" ]; then base_yaml=3D"${base_=
yaml}:kas/opt/encrypt-data.yml"; fi<br />- if [ "${factory_reset}" =3D "ena=
ble" ]; then base_yaml=3D"${base_yaml}:kas/opt/factory-reset.yml"; fi<br />=
@@ -399,6 +401,57 @@ build:qemu-arm-base-sid:<br />separate_home_partition:=
 enable<br />deploy: enable<br /><br />+# forky image builds<br />+.build_b=
ase_forky:<br />+ extends:<br />+ - .build_base<br />+ rules:<br />+ - if: =
$CI_COMMIT_TAG<br />+ when: never<br />+ - if: '$CI_PIPELINE_SOURCE =3D=3D =
"schedule" &amp;&amp; $CI_RUN_UNSTABLE'</blockquote>
I meant we should migrate both forky and sid under this one<br />CI_RUN_UNS=
TABLE variable. Now we would still have two of them and would<br />need to =
set them both in the pipeline schedule.</blockquote>
</div>
<div>My idea was as below,&nbsp;</div>
<div>
<p class=3D"MsoPlainText">- The CI variable CI_RUN_UNSTABLE_FORKY is change=
d to CI_RUN_UNSTABLE,</p>
<p class=3D"MsoPlainText"><span style=3D"mso-spacerun: yes;">&nbsp; </span>=
however CI_RUN_UNSTABLE_SID is not changed in this patch series, will</p>
<p class=3D"MsoPlainText"><span style=3D"mso-spacerun: yes;">&nbsp; </span>=
update in a separate patch as it is not related to this series.</p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText">And it was mentioned in the v2 patch series cover=
 letter, I think you would have missed that.&nbsp;</p>
<p class=3D"MsoPlainText">let me know if required I will change CI_RUN_UNST=
ABLE_SID to CI_RUN_UNSTABLE in this series only.</p>
<p class=3D"MsoPlainText">&nbsp;</p>
</div>
</blockquote>
<div>
<p class=3D"MsoPlainText">Any comments on this? Shall i include the above c=
hange in this patch series?&nbsp;</p>
<p class=3D"MsoPlainText">please let me know, will send v3 patch series acc=
ordingly.&nbsp;</p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText">Thanks &amp; Regards</p>
<p class=3D"MsoPlainText">Shivanand K&nbsp;</p>
</div>
</div>

--lSRfHyARIEp7cY4WKtoL--