From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 11843C5518E for ; Mon, 3 Aug 2026 09:47:32 +0000 (UTC) Subject: Re: [isar-cip-core][PATCH v2 2/2] Enable CI image build and test support for forky To: cip-dev@lists.cip-project.org From: "Kunijadar Shivanand" X-Originating-Location: Hyderabad, Telangana, IN (151.186.148.44) X-Originating-Platform: Windows Chrome 150 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Mon, 03 Aug 2026 02:47:24 -0700 References: <20260728085519.3615499-1-Shivanand.Kunijadar@toshiba-tsip.com> <20260728085519.3615499-3-Shivanand.Kunijadar@toshiba-tsip.com> <1fc13594-a7c6-421c-82fc-e8953bd07458@siemens.com> <1113502.1785299204099110509@lists.cip-project.org> In-Reply-To: <1113502.1785299204099110509@lists.cip-project.org> Message-ID: <1187398.1785750444675558966@lists.cip-project.org> Content-Type: multipart/alternative; boundary="lSRfHyARIEp7cY4WKtoL" List-Id: X-Webhook-Received: from 45-33-107-173.ip.linodeusercontent.com [45.33.107.173] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Mon, 03 Aug 2026 09:47:32 -0000 X-Groupsio-URL: https://lists.cip-project.org/g/cip-dev/message/23853 --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, Shivanand.Kunijadar@toshiba-tsip.com wrote: >>=20 >>> From: Shivanand Kunijadar >>>=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 >>> --- >>> .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 >>> # Quirin Gylstorff >>> # Nobuhiro Iwamatsu >>> +# Shivanand Kunijadar >>> # >>> # 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
Hi Jan, 
 
On Tue, Jul 28, 2026 at 09:26 PM, Kunijadar Shivanand wrote:
On Tue, Jul 28, 2026 at 08:29 AM, Jan Kiszka wrote:
On 28.07.26 10:55, Shivanand.Kunijadar@toshiba-tsip.com wrote:<= br />
From: Shivanand Kunijadar <Shivanand.Kunijadar@toshiba-tsip.= com>

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
rele= ased and there will always be some build & test issues.

It i= ncludes SWUpdate, secure boot & RB tests.

Signed-off-by: Shi= vanand Kunijadar <Shivanand.Kunijadar@toshiba-tsip.com>
---
.gitlab-ci.yml | 148 +++++++++++++++++++++++++++++++++++++
.reproduci= ble-check-ci.yml | 72 ++++++++++++++++++
2 files changed, 220 insertio= ns(+)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index b5= 3def4..b15c5da 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml@@ -8,6 +8,7 @@
# Jan Kiszka <jan.kiszka@siemens.com>
#= Quirin Gylstorff <quirin.gylstorff@siemens.com>
# Nobuhiro Iwam= atsu <nobuhiro1.iwamatsu@toshiba.co.jp>
+# Shivanand Kunijadar &= lt;shivanand.kunijadar@toshiba-tsip.com>
#
# SPDX-License-Iden= tifier: 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 bas= e_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 "ena= ble" ]; 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

+# forky image builds
+.build_b= ase_forky:
+ extends:
+ - .build_base
+ rules:
+ - if: = $CI_COMMIT_TAG
+ when: never
+ - if: '$CI_PIPELINE_SOURCE =3D=3D = "schedule" && $CI_RUN_UNSTABLE'
I meant we should migrate both forky and sid under this one
CI_RUN_UNS= TABLE variable. Now we would still have two of them and would
need to = set them both in the pipeline schedule.
My idea was as below, 

- The CI variable CI_RUN_UNSTABLE_FORKY is change= d to CI_RUN_UNSTABLE,

  = however CI_RUN_UNSTABLE_SID is not changed in this patch series, will

  = update in a separate patch as it is not related to this series.

 

And it was mentioned in the v2 patch series cover= letter, I think you would have missed that. 

let me know if required I will change CI_RUN_UNST= ABLE_SID to CI_RUN_UNSTABLE in this series only.

 

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

please let me know, will send v3 patch series acc= ordingly. 

 

Thanks & Regards

Shivanand K 

--lSRfHyARIEp7cY4WKtoL--