From: Paul Eggleton <paul.eggleton@linux.microsoft.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] classes: add new retain class for retaining build results
Date: Sun, 28 Jul 2024 17:22:42 -0700 [thread overview]
Message-ID: <cover.1722211934.git.paul.eggleton@linux.microsoft.com> (raw)
Add a fairly simple class to tar up the work directory on task failure
to a configurable location - useful when the build environment is
ephemeral (e.g. an autobuilder/build pipeline). The directories that
are retained can be configured, and you can also choose to save
directories on every build as well if desired.
[This is a significant reworking of a prototype I sent as an RFC back
in 2020 (AKA "workdir_save"). Changes since then include deferring
tarball creation until the end, more config flexibility, and the
addition of test cases.]
The following changes since commit 662396533177b72cc1d83e95841b27f7e42dcb20:
create-spdx-3.0/populate_sdk_base: Add SDK_CLASSES inherit mechanism to fix tarball SPDX manifests (2024-07-26 12:26:24 +0100)
are available in the git repository at:
https://git.yoctoproject.org/poky-contrib paule/retain
https://git.yoctoproject.org/poky-contrib/log/?h=paule/retain
(should have been openembedded-core-contrib I know, but for some reason
I wasn't able to push there.)
Paul Eggleton (1):
classes: add new retain class for retaining build results
meta/classes-global/retain.bbclass | 162 ++++++++++++++++++++++++
meta/lib/oeqa/selftest/cases/retain.py | 219 +++++++++++++++++++++++++++++++++
2 files changed, 381 insertions(+)
create mode 100644 meta/classes-global/retain.bbclass
create mode 100644 meta/lib/oeqa/selftest/cases/retain.py
--
1.8.3.1
next reply other threads:[~2024-07-29 0:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 0:22 Paul Eggleton [this message]
2024-07-29 0:22 ` [PATCH 1/1] classes: add new retain class for retaining build results Paul Eggleton
2024-07-30 8:13 ` [OE-core] " Richard Purdie
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=cover.1722211934.git.paul.eggleton@linux.microsoft.com \
--to=paul.eggleton@linux.microsoft.com \
--cc=openembedded-core@lists.openembedded.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