summaryrefslogtreecommitdiffstats
path: root/COPYING.MIT
diff options
context:
space:
mode:
authorStefan Agner <stefan.agner@toradex.com>2020-04-28 16:28:14 +0000
committerStefan Agner <stefan.agner@toradex.com>2020-05-07 21:06:55 +0000
commitfcc397f16efde0c053c8a96e7500147ab84cb8d3 (patch)
tree59fbdb32eb6c13ce0adcfe72aad89fcf0aa5e703 /COPYING.MIT
parent82d7e04924f847bccba3136d1602d5646486a926 (diff)
downloadmeta-updater-fcc397f16efde0c053c8a96e7500147ab84cb8d3.tar.gz
image_types_ostree/ota: use hash from ostree commit
Relying on a OSTree branch reference has been problematic in the past and addressed by adding more attributes to it in commit 202a8c70ba8c ("image_types_ostree: Add a unique ref to fix simultaneous bitbaking."). However, depening on what kind of OpenEmbedded builds are running in parallel, even more attributes would need to be taken into account. Instead of relying on a reference, store the exact ostree commit hash in a manifest file and reuse it in the do_image_ota deploy task. This guarantees that the correct reference gets picked even when two builds with the exact same machine/image name run in parallel. Note: This gets rid of the second branch name again. If the branch name with image name is preferred, the variable OSTREE_BRANCHNAME can be used: OSTREE_BRANCHNAME = "${SOTA_HARDWARE_ID}-${IMAGE_BASENAME}" Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Diffstat (limited to 'COPYING.MIT')
0 files changed, 0 insertions, 0 deletions