RE: [isar-cip-core][PATCH v4 0/3] Enable Debian Sid support

Hi Jan, 

Thank you for the minor changes. 

I have one request, the scheduled pipeline "Weekly Debian Sid build & tests" here https://gitlab.com/cip-project/cip-core/isar-cip-core/-/pipeline_schedules was used for testing, but I'm unable to change the branch to "next" due to the below error. 

"The current user is not authorized to update the pipeline schedule" 

Could you please create new scheduled pipeline using "next" branch with same options (if interval & time zone are fine)? 
Make sure to define CI variable "CI_RUN_UNSTABLE_SID" in this pipeline. 

Thanks & Regards
Shivanand K

-----Original Message-----
From: Jan Kiszka <[email protected]> 
Sent: 23 June 2026 18:12
To: kunijadar shivanand(ＴＳＩＰ DITC_DIT-OST) <[email protected]>; [email protected]
Cc: balakumar adithya(ＴＳＩＰ ＤＩＴＣ＿ＤＩＴ-ＯＳＴ) <[email protected]>; dinesh kumar(ＴＳＩＰ DITC_DIT-OST) <[email protected]>; hayashi kazuhiro(林 和宏 □ＤＩＴＣ○ＣＰＴ) <[email protected]>
Subject: Re: [isar-cip-core][PATCH v4 0/3] Enable Debian Sid support

On 23.06.26 12:52, Shivanand Kunijadar wrote:
> This enables the support to build Debian sid based images in the 
> repository including CI (scheduled jobs) which helps to detect the issues in advance.
> 
> I've confirmed the Sid image boot works for SWUpdate & Data encryption enabled images.
> 
> The scheduled job is created here 
> https://gitlab.com/cip-project/cip-core/isar-cip-core/-/pipeline_sched
> ules and confirmed the jobs are getting triggered for "Weekly Debian 
> Sid build & tests". Once this series is merged we can change branch to 
> "next" and update the interval if required. please note that a new CI 
> variable is introduced for these builds (i.e CI_RUN_UNSTABLE_SID) and 
> the same is being used in the CI jobs.
> 
> For the sid, I selected IEC security image as build and test targets 
> as it includes all the features (swupdate, secure boot, data encryption, factory reset).
> The idea is to have minimal jobs to test more feature. I understand 
> that in the IEC jobs we will not test swupdate, factory reset explicitly.
> if required we can also add swupdate, secure boot job targets for sid 
> as well, please let me know your opinion.
> 
> At the moment, the security image build jobs are passing for amd64, arm64 & armhf archs.
> The test jobs are failed as it needs some adjustments in the 
> `submit-lava.sh` script so I plan to handle it in a separate patch. I hope this is fine at the moment.
> please let us know if you have any different opinion.
> 
> Shivanand Kunijadar (3):
>   Add the default kernel verions in cip-core-common.inc with extra weak
>   Enable Debian Sid support
>   Enable CI image build and test support for Sid
> 
>  .gitlab-ci.yml                                | 90 +++++++++++++++++++
>  Kconfig                                       |  4 +
>  conf/distro/cip-core-common.inc               |  3 +
>  conf/distro/cip-core-sid.conf                 | 13 +++
>  conf/distro/cip-core-trixie.conf              |  3 -
>  kas/opt/sid.yml                               | 15 ++++
>  .../initramfs-crypt-hook_0.11.bb              |  2 +
>  start-qemu.sh                                 |  2 +
>  8 files changed, 129 insertions(+), 3 deletions(-)  create mode 
> 100644 conf/distro/cip-core-sid.conf  create mode 100644 
> kas/opt/sid.yml
> 

Thanks, applied with that tweaks on patch 2.

Jan

--
Siemens AG, Foundational Technologies
Linux Expert Center