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 v3 0/3] Enable debian forky build & test support
Date: Tue, 11 Aug 2026 23:17:27 -0700	[thread overview]
Message-ID: <1473907.1786515447555873268@lists.cip-project.org> (raw)
In-Reply-To: <c8b01319-b1a0-4d43-9707-b12acb2ff19f@siemens.com>

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

On Tue, Aug 11, 2026 at 10:09 AM, Jan Kiszka wrote:

> 
> On 11.08.26 11:04, Shivanand.Kunijadar@toshiba-tsip.com wrote:
> 
>> From: Shivanand Kunijadar <Shivanand.Kunijadar@toshiba-tsip.com>
>> 
>> This patch series adds the debian forky based image build & CI test
>> support.
>> 
>> It enables SWUpdate, secure boot, security tests in LAVA and RB in gitlab
>> CI.
>> 
>> NOTE:
>> - The existing .reproducible-check-ci.yml is updated to support forky
>> images reproducibility check. No need to add the exta scheduled pipeline
>> for forky, the current scheduled pipeline covers both trixie and
>> forky. The forky builds and RB tests are kept with allowed failure
>> option as true.
>> - Updated authors list for .gitlab-ci.yml & .reproducible-check-ci.yml
>> 
>> Shivanand Kunijadar (3):
>> .gitlab-cip.yml: Change CI variable to CI_RUN_UNSTABLE
>> Enable the support of Debian forky based builds
>> Enable CI image build and test support for forky
>> 
>> .gitlab-ci.yml | 152 +++++++++++++++++-
>> .reproducible-check-ci.yml | 72 +++++++++
>> Kconfig | 4 +
>> conf/distro/cip-core-forky.conf | 13 ++
>> kas/opt/forky.yml | 15 ++
>> .../files/forky/PkKek-1-snakeoil.key | 30 ++++
>> .../files/forky/PkKek-1-snakeoil.pem | 23 +++
>> .../swupdate-certificates/files/forky | 1 +
>> start-qemu.sh | 2 +
>> 9 files changed, 310 insertions(+), 2 deletions(-)
>> create mode 100644 conf/distro/cip-core-forky.conf
>> create mode 100644 kas/opt/forky.yml
>> create mode 100644
>> recipes-devtools/secure-boot-secrets/files/forky/PkKek-1-snakeoil.key
>> create mode 100644
>> recipes-devtools/secure-boot-secrets/files/forky/PkKek-1-snakeoil.pem
>> create mode 120000 recipes-devtools/swupdate-certificates/files/forky
> 
> Thanks, applied.

Thank you.

You may need to update CI variable in pipeline schedules  if not updated.
please change CI_RUN_UNSTABLE_SID to CI_RUN_UNSTABLE which triggers both forky & sid jobs.

Also change the name "Weekly Debian sid & testing builds & checks" to include forky as well.

Thanks & Regards
Shivanand K

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

      reply	other threads:[~2026-08-12  6:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11  9:04 [isar-cip-core][PATCH v3 0/3] Enable debian forky build & test support Shivanand.Kunijadar
2026-08-11  9:04 ` [isar-cip-core][PATCH v3 1/3] .gitlab-cip.yml: Change CI variable to CI_RUN_UNSTABLE Shivanand.Kunijadar
2026-08-11  9:04 ` [isar-cip-core][PATCH v3 2/3] Enable the support of Debian forky based builds Shivanand.Kunijadar
2026-08-11  9:04 ` [isar-cip-core][PATCH v3 3/3] Enable CI image build and test support for forky Shivanand.Kunijadar
2026-08-11 17:09 ` [isar-cip-core][PATCH v3 0/3] Enable debian forky build & test support Jan Kiszka
2026-08-12  6:17   ` Kunijadar Shivanand [this message]

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=1473907.1786515447555873268@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