public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH 0/6] Fix essentials rebuild and cover with CI
Date: Fri, 21 Feb 2025 17:48:37 +0200	[thread overview]
Message-ID: <20250221154843.515037-1-amikan@ilbers.de> (raw)

Add sed package as an example of rebuiled essential package to be used
during the build inside sbuild chroot.

This patchset fixes the following use case:

$ bitbake -c build sed
$ echo -e "\npython do_rootfs_install:append() {\n\n}" >> /work/meta/classes/rootfs.bbclass
$ bitbake -c build sed

Cover it with full CI, also cover f62de6792 with the following case:

$ bitbake -c local_isarapt cowsay
$ bitbake -c build sed
$ bitbake -c cleansstate sbuild-chroot-target
$ bitbake -c build cowsay

Also introduce new CI APIs:
- Obtaining of package version installed in rootfs.
- Inserting custom sbuild hooks during test case.

Anton Mikanovich (6):
  CI: Add API for checking package version in rootfs
  CI: Add API for sbuild hook insertion
  CI: Add sed as essential rebuild test package
  CI: Add essential packages rebuild test case
  CI: Fix getVars API on fast recalling
  meta: Do not update isar-apt during sbuild chroot prepare

 meta-test/recipes-extended/sed/sed.bb         |  15 +++
 .../sbuild-chroot/sbuild-chroot.inc           |   8 +-
 testsuite/cibase.py                           | 101 ++++++++++++++++++
 testsuite/cibuilder.py                        |  26 ++++-
 testsuite/citest.py                           |  25 ++++-
 testsuite/utils.py                            |   6 ++
 6 files changed, 178 insertions(+), 3 deletions(-)
 create mode 100644 meta-test/recipes-extended/sed/sed.bb

-- 
2.34.1

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20250221154843.515037-1-amikan%40ilbers.de.

             reply	other threads:[~2025-02-21 15:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 15:48 Anton Mikanovich [this message]
2025-02-21 15:48 ` [PATCH 1/6] CI: Add API for checking package version in rootfs Anton Mikanovich
2025-02-21 15:48 ` [PATCH 2/6] CI: Add API for sbuild hook insertion Anton Mikanovich
2025-02-21 15:48 ` [PATCH 3/6] CI: Add sed as essential rebuild test package Anton Mikanovich
2025-02-21 15:48 ` [PATCH 4/6] CI: Add essential packages rebuild test case Anton Mikanovich
2025-02-21 15:48 ` [PATCH 5/6] CI: Fix getVars API on fast recalling Anton Mikanovich
2025-02-21 15:48 ` [PATCH 6/6] meta: Do not update isar-apt during sbuild chroot prepare Anton Mikanovich
2025-02-21 16:34   ` 'Jan Kiszka' via isar-users
2025-03-03 10:13     ` Anton Mikanovich
2025-03-03 14:32       ` 'Jan Kiszka' via isar-users
2025-03-03 15:16         ` Anton Mikanovich

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=20250221154843.515037-1-amikan@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=isar-users@googlegroups.com \
    /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