7966 2015-07-07 21:19:43 +0000 buildhistory should write git SHAs 2015-09-03 12:07:00 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain 1.9 All Multiple VERIFIED FIXED Low enhancement 1.9 1 ross.burton bluelightning bogdanx.a.voiculescu meta.mr.watcher meta.watcher bogdanx.a.voiculescu --- --- No (bug/feature does not impact docs) oldest_to_newest 52197 0 ross.burton 2015-07-07 21:19:43 +0000 It would be awesome if buildhistory could detect if it were running in a git repo and write the layer SHAs to the repo somewhere, like bitbake does when it starts up. When my buildhistory log is "bitbake core-image-sato" 20 times it would help to differentiate what build was what. 52198 1 bluelightning 2015-07-07 22:14:08 +0000 Unless I'm misunderstanding the request, it already does this in two places - metadata-revs at the root of the buildhistory repo (machine-readable, written out on every build), and build-id.txt under the directory for an image (only written when building an image, and the format is the same as bitbake's preamble output). 52200 2 ross.burton 2015-07-07 22:33:48 +0000 You're not mistaken. Would it be convenient/possible/useful to put this into the commit log to? 53578 3 bluelightning 2015-08-31 21:43:43 +0000 Implemented in master: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=734411a9e633f5b1459216e4cc5175f267d8a668 53676 4 bogdanx.a.voiculescu 2015-09-03 12:07:00 +0000 Verified on master: cat buildhistory/metadata-revs meta = master:71b0568fa43285f0946fae93fb43cea5f3bbecec meta-yocto = master:71b0568fa43285f0946fae93fb43cea5f3bbecec meta-yocto-bsp = master:71b0568fa43285f0946fae93fb43cea5f3bbece