Skip to content

introduce multi-state image deployment

Bartosz Golaszewski openembedded-core 2 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest2 patches 3 repliesIn review
  2. v1 RFC2 patches 5 repliesSuperseded

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2qemuboot.bbclass: don't redefine IMGDEPLOYDIRmeta/classes/qemuboot.bbclass+0 -10 replies
2/2image.bbclass: deploy image artifacts in stagesmeta/classes/image.bbclass meta/classes/sstate.bbclass+21 -03 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [OE-core][PATCH v2 0/2] introduce multi-state image deployment

From: Bartosz Golaszewski <[email protected]>

Hi Richard et al,

This is another shot at multi-stage image deployment. This time around I managed to fix the problem with changing task hashes and anonymous python functions ordering by simply moving the code assigning pre- and postfuncs for sstate into an even handler invoked right after all anonymous python code is run. Seems to work fine and there's no need to deltask do_package anymore.

Just like before: each image task becomes an sstate task and handles the deployment of the artifacts it generates. Files created by tasks other than IMAGE_CMD are still deployed by do_image_complete.

The dm-verity problem I'm trying to solve is described here:
https://lists.openembedded.org/g/openembedded-core/message/136203

Bartosz Golaszewski (2):
qemuboot.bbclass: don't redefine IMGDEPLOYDIR
image.bbclass: deploy image artifacts in stages

 meta/classes/image.bbclass    | 17 +++++++++++++++++
 meta/classes/qemuboot.bbclass |  1 -
 meta/classes/sstate.bbclass   |  4 ++++
 3 files changed, 21 insertions(+), 1 deletion(-)
Signature · 1 line
2.25.0