From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v3 0/6] Provide list of deployment artifacts
Date: Thu, 1 Sep 2016 11:55:57 +0300 [thread overview]
Message-ID: <cover.1472719962.git.ed.bartosh@linux.intel.com> (raw)
Hi,
This is a fix for Bug #9869 - Provide a per-target manifest of files which were, or would have been, produced
The list of artifacts produced by deployment tasks (do_deploy, do_image_complete and do_populate_sdk[_ext] is
obtained from sstate manifests and fired as a TaskArtifacts metadata event. This should allow Toaster to
handle artifacts in simple way and remove a lot of current Toaster code doing guess work.
To generate manifests for do_image_complete and do_populate_sdk they have been put under sstate control.
To avoid storing big files(images and sdk installer) in sstate new variable SSTATE_SKIP_CREATION has been
set in image.bbclass and populate_sdk_base.bbclass and sstate code was modified to avoid adding files
to sstate if SSTATE_SKIP_CREATION is set.
Changes in v2: Reorganized patchset to make it bisectable (Thanks Richard)
Used task in the name of DEPLOYDIR to avoid using the same directory for different tasks of the same recipe
Changes in v3: Fixed bug that caused deletion of image manifest
The following changes since commit 087c580b286816265f487e02746bfa6e26081554:
init-install: Fixes the install script failing when not finding any mmcblk devices (2016-08-30 07:57:50 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ed/oe-core/artifacts-9869
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ed/oe-core/artifacts-9869
Ed Bartosh (6):
image: populate_sdk_base: add DEPLOYDIR variable
sstate.bbclass: skip packaging if SSTATE_SKIP_CREATION is set
image: populate_sdk: deploy images to DEPLOYDIR
image.bbclass: put image_complete under sstate control
populate_sdk_base: put populate_sdk under sstate control
toaster: fire TaskArtifacts event
meta/classes/image-live.bbclass | 12 +++---
meta/classes/image-vm.bbclass | 22 +++++------
meta/classes/image.bbclass | 15 ++++++--
meta/classes/image_types.bbclass | 44 +++++++++++-----------
meta/classes/image_types_uboot.bbclass | 2 +-
meta/classes/populate_sdk_base.bbclass | 27 ++++++++-----
meta/classes/rootfs-postcommands.bbclass | 4 +-
meta/classes/sstate.bbclass | 2 +
meta/classes/syslinux.bbclass | 2 +-
meta/classes/toaster.bbclass | 17 +++++++++
meta/lib/oe/rootfs.py | 6 +--
meta/lib/oeqa/selftest/imagefeatures.py | 4 +-
.../images/build-appliance-image_15.0.0.bb | 8 ++--
13 files changed, 99 insertions(+), 66 deletions(-)
--
Ed
next reply other threads:[~2016-09-01 8:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 8:55 Ed Bartosh [this message]
2016-09-01 8:55 ` [PATCH v3 1/6] image: populate_sdk_base: add DEPLOYDIR variable Ed Bartosh
2016-09-01 8:55 ` [PATCH v3 2/6] sstate.bbclass: skip packaging if SSTATE_SKIP_CREATION is set Ed Bartosh
2016-09-01 8:56 ` [PATCH v3 3/6] image: populate_sdk: deploy images to DEPLOYDIR Ed Bartosh
2016-09-01 8:56 ` [PATCH v3 4/6] image.bbclass: put image_complete under sstate control Ed Bartosh
2016-09-01 8:56 ` [PATCH v3 5/6] populate_sdk_base: put populate_sdk " Ed Bartosh
2016-09-01 8:56 ` [PATCH v3 6/6] toaster: fire TaskArtifacts event Ed Bartosh
2016-09-02 11:45 ` [PATCH v3 0/6] Provide list of deployment artifacts 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.1472719962.git.ed.bartosh@linux.intel.com \
--to=ed.bartosh@linux.intel.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