CIP-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Kunijadar Shivanand" <Shivanand.Kunijadar@toshiba-tsip.com>
To: cip-dev@lists.cip-project.org
Subject: Re: [isar-cip-core][PATCH v2 2/2] Enable CI image build and test support for forky
Date: Mon, 03 Aug 2026 02:47:24 -0700	[thread overview]
Message-ID: <1187398.1785750444675558966@lists.cip-project.org> (raw)
In-Reply-To: <1113502.1785299204099110509@lists.cip-project.org>

[-- Attachment #1: Type: text/plain, Size: 3293 bytes --]

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:
>> 
>>> 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
>>> released and there will always be some build & test issues.
>>> 
>>> It includes SWUpdate, secure boot & RB tests.
>>> 
>>> Signed-off-by: Shivanand Kunijadar <Shivanand.Kunijadar@toshiba-tsip.com>
>>> ---
>>> .gitlab-ci.yml | 148 +++++++++++++++++++++++++++++++++++++
>>> .reproducible-check-ci.yml | 72 ++++++++++++++++++
>>> 2 files changed, 220 insertions(+)
>>> 
>>> 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 <jan.kiszka@siemens.com>
>>> # Quirin Gylstorff <quirin.gylstorff@siemens.com>
>>> # Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
>>> +# Shivanand Kunijadar <shivanand.kunijadar@toshiba-tsip.com>
>>> #
>>> # SPDX-License-Identifier: MIT
>>> #
>>> @@ -63,6 +64,7 @@ default:
>>> - if [ "${release}" = "bullseye" ]; then
>>> base_yaml="${base_yaml}:kas/opt/bullseye.yml"; fi
>>> - if [ "${release}" = "bookworm" ]; then
>>> base_yaml="${base_yaml}:kas/opt/bookworm.yml"; fi
>>> - if [ "${release}" = "trixie" ]; then
>>> base_yaml="${base_yaml}:kas/opt/trixie.yml"; fi
>>> + - if [ "${release}" = "forky" ]; then
>>> base_yaml="${base_yaml}:kas/opt/forky.yml"; fi
>>> - if [ "${release}" = "sid" ]; then
>>> base_yaml="${base_yaml}:kas/opt/sid.yml"; fi
>>> - if [ "${encrypt}" = "enable" ]; then
>>> base_yaml="${base_yaml}:kas/opt/encrypt-data.yml"; fi
>>> - if [ "${factory_reset}" = "enable" ]; then
>>> base_yaml="${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_base_forky:
>>> + extends:
>>> + - .build_base
>>> + rules:
>>> + - if: $CI_COMMIT_TAG
>>> + when: never
>>> + - if: '$CI_PIPELINE_SOURCE == "schedule" && $CI_RUN_UNSTABLE'
>> 
>> 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.
> 
> 
> My idea was as below,
> 
> 
> - The CI variable CI_RUN_UNSTABLE_FORKY is changed 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_UNSTABLE_SID to
> CI_RUN_UNSTABLE in this series only.
> 
> 
> 
> 
> 
> 
> 

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

[-- Attachment #2: Type: text/html, Size: 3846 bytes --]

  reply	other threads:[~2026-08-03  9:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28  8:55 [isar-cip-core][PATCH v2 0/2] Enable debian forky build & test support Shivanand.Kunijadar
2026-07-28  8:55 ` [isar-cip-core][PATCH v2 1/2] Enable the support of Debian forky based builds Shivanand.Kunijadar
2026-07-28  8:55 ` [isar-cip-core][PATCH v2 2/2] Enable CI image build and test support for forky Shivanand.Kunijadar
2026-07-28 15:29   ` Jan Kiszka
2026-07-29  4:26     ` Kunijadar Shivanand
2026-08-03  9:47       ` Kunijadar Shivanand [this message]
2026-08-10 14:45         ` Jan Kiszka
2026-08-11  9:20           ` Kunijadar Shivanand

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=1187398.1785750444675558966@lists.cip-project.org \
    --to=shivanand.kunijadar@toshiba-tsip.com \
    --cc=cip-dev@lists.cip-project.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox