From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: adriaan.schmidt@siemens.com, Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH 0/6] Imager schroot migration
Date: Sat, 14 May 2022 10:07:30 +0300 [thread overview]
Message-ID: <20220514070736.12997-1-amikan@ilbers.de> (raw)
This is the first version of full Isar migration from buildchroot to schroot
usage as the next step after moving to sbuild.
Imagers of every target are now running in separate schroot sessions with
independent overlays on top of basic unchanged schroot. It means we need to
open schroot session before any imager task execution and close this session
after the usage. Any changes made inside overlay will be dropped after the
usage to keep basic schroot clean.
We also need to introduce additional cleanup inside isar-events finish handler
to prevent leaving sessions in case we execute only session start task.
There are still couple of issues need to be solved before the usage:
- it works only after reverting of 4e1dacc
- there are no documentaion updates
- only basic build scenarios works, CI still fails
Anton Mikanovich (6):
sbuild: Allow setting custom config paths
base: Implement bitbake build ID
imager: Migrate from buildchroot to schroot
imager: Move image types to schroot
events: Cleanup lost schroot sessions if any
meta: Remove buildchroot
meta-isar/conf/local.conf.sample | 2 +-
meta/classes/base.bbclass | 9 ++
meta/classes/buildchroot.bbclass | 71 ----------------
meta/classes/dpkg-base.bbclass | 28 ------
meta/classes/image-tools-extension.bbclass | 80 ++++++++++++++---
meta/classes/image.bbclass | 19 +----
meta/classes/imagetypes_vm.bbclass | 7 +-
meta/classes/imagetypes_wic.bbclass | 73 +++++-----------
meta/classes/isar-events.bbclass | 19 ++++-
meta/classes/sbuild.bbclass | 50 ++++++++---
meta/conf/bitbake.conf | 3 -
.../buildchroot/buildchroot-host.bb | 24 ------
.../buildchroot/buildchroot-target.bb | 15 ----
.../buildchroot/buildchroot.inc | 85 -------------------
.../buildchroot/files/build.sh | 17 ----
.../buildchroot/files/common.sh | 32 -------
.../buildchroot/files/configscript.sh | 15 ----
.../buildchroot/files/deps.sh | 47 ----------
18 files changed, 161 insertions(+), 435 deletions(-)
delete mode 100644 meta/classes/buildchroot.bbclass
delete mode 100644 meta/recipes-devtools/buildchroot/buildchroot-host.bb
delete mode 100644 meta/recipes-devtools/buildchroot/buildchroot-target.bb
delete mode 100644 meta/recipes-devtools/buildchroot/buildchroot.inc
delete mode 100644 meta/recipes-devtools/buildchroot/files/build.sh
delete mode 100644 meta/recipes-devtools/buildchroot/files/common.sh
delete mode 100644 meta/recipes-devtools/buildchroot/files/configscript.sh
delete mode 100644 meta/recipes-devtools/buildchroot/files/deps.sh
--
2.17.1
next reply other threads:[~2022-05-14 7:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 7:07 Anton Mikanovich [this message]
2022-05-14 7:07 ` [PATCH 1/6] sbuild: Allow setting custom config paths Anton Mikanovich
2022-05-14 7:07 ` [PATCH 2/6] base: Implement bitbake build ID Anton Mikanovich
2022-05-14 7:07 ` [PATCH 3/6] imager: Migrate from buildchroot to schroot Anton Mikanovich
2022-05-14 7:07 ` [PATCH 4/6] imager: Move image types " Anton Mikanovich
2022-05-14 7:07 ` [PATCH 5/6] events: Cleanup lost schroot sessions if any Anton Mikanovich
2022-05-14 7:07 ` [PATCH 6/6] meta: Remove buildchroot 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=20220514070736.12997-1-amikan@ilbers.de \
--to=amikan@ilbers.de \
--cc=adriaan.schmidt@siemens.com \
--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