From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [RFC v2 0/3] PoC for isar-apt repo reusing
Date: Mon, 13 Jun 2022 09:07:56 +0200 [thread overview]
Message-ID: <20220613070759.16949-1-ubely@ilbers.de> (raw)
Currently, isar-apt repo is always rebuilt at second build when
temporary files except the repo directory were deleted.
This patchset implements proof-of-concept of reusing isar-apt
repo previously built. The idea is to check that package already
exists in the repo and early exit tasks related to fetching/building.
Such approach doesn't remove any tasks from the queue, but changes
their behvaior (early exit) in case of existing package found.
Using this feature doesn't depend on sstate-cache and requires only
local repo from some of previous builds to exist.
Changes since v1:
- avocado test, not based on build time measure
- fixed isar-apt check in compat-arch mode
Uladzimir Bely (3):
meta: Reuse existing local isar-apt repo in new builds
doc: Add section for isar-apt reuse functionality
ci: Added test for isar-apt reuse functionality
doc/user_manual.md | 23 ++++++++++
meta-isar/conf/local.conf.sample | 4 ++
meta/classes/dpkg-base.bbclass | 1 +
meta/classes/isar-apt-cache.bbclass | 69 +++++++++++++++++++++++++++++
testsuite/cibase.py | 42 ++++++++++++++++++
testsuite/cibuilder.py | 7 ++-
testsuite/citest.py | 12 +++++
7 files changed, 157 insertions(+), 1 deletion(-)
create mode 100644 meta/classes/isar-apt-cache.bbclass
--
2.20.1
next reply other threads:[~2022-06-13 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 7:07 Uladzimir Bely [this message]
2022-06-13 7:07 ` [RFC v2 1/3] meta: Reuse existing local isar-apt repo in new builds Uladzimir Bely
2022-06-13 7:07 ` [RFC v2 2/3] doc: Add section for isar-apt reuse functionality Uladzimir Bely
2022-06-13 7:07 ` [RFC v2 3/3] ci: Added test " Uladzimir Bely
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=20220613070759.16949-1-ubely@ilbers.de \
--to=ubely@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