There is a need in several enhancements in the buildhistory to preserve technical information about official builds done in the past and tracking changes in key aspects of that information. For every single official build we need to store information about: - set of recipes that we used in builds, including information like checksum, originated layer(s), .bbappend and other overrides. - information about source/patch files used in recipes (URLs, layers originating from, checksums). - for images, links to source recipe names/versions that was used in image. Rationale: provide information for debugging if something in environment was altered via *.conf in the build system.
To be honest, this sounds like significant feature creep compared to what buildhistory was designed/intended for. My suggestion is we'd look at a way to extend buildhistory so that you can customise the data it logs from an additional layer rather than add this to the core directly.
Created attachment 2689 [details] buildhistory extension bbclass
I have sent one change that is needed to make this possible to extend, it's part of this patchset: http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/buildhistory-fixes10 I've also attached an extension class that does as this bug requests.
Note that the only fix required from the above patchset is this one: http://cgit.openembedded.org/openembedded-core-contrib/commit/?h=paule/buildhistory-fixes10&id=09068165771ebdfde43d13b08e757e49c3e56750
The aforementioned patchset has been merged to master.
Paul, we have tried that class, looks great from first look. Few comments: 1. sha256 sums to be used instead of md5. or both. we have in recipes both, it make sense to have matching information stored in history. 2. common path from top build dir should be stripped. doesn’t make sense to report /home/user/git/distro/meta/recipes-core/something/files/xxx.patch where most relevant information is ./meta/recipes-core/something/files/xxx.patch I think having relative path against build root directory has more value than absolute paths, in most cases. Absolute path only make sense if some files are located outside of build top dir. 3. in image data, installed-package-recipes.txt seems doesn’t have revision (and maybe epoch?) field $ grep shadow-securetty installed-package-recipes.txt installed-packages.txt installed-package-recipes.txt:shadow-securetty 4.2.1 shadow-securetty installed-packages.txt:shadow-securetty-4.2.1-r3.qemux86.rpm $ shouldn't it be something similar to $PF format ?
Created attachment 2780 [details] buildhistory extension bbclass v2 OK, updated class with requested changes attached.
Verified on master: e1aa897beb33171bc902207b98c8f666b9e97ad3 Additional detailed information about builds is stored.