6770 2014-09-26 17:08:33 +0000 Improve storing build information in images 2014-11-10 16:18:51 +0000 1 1 7 Build System, Metadata & Runtime OE-Core deployment unspecified x86 Multiple RESOLVED FIXED Medium enhancement 1.8 1 philip alejandro.hernandez bluelightning doug.geiger kergoth sgw --- --- Yes (doc changes required) oldest_to_newest 45902 0 philip 2014-09-26 17:08:33 +0000 Currently images contain a file /etc/version in the image that contains a timestamp. root@ettus-e300:/etc/init.d# cat /etc/version 201409231521 It would be helpful to have a standard way of documenting what layers, versions of layers, bitbake versions, etc were used to create the image. From a brief discussion on the list, it seems like there are several ad hoc solutions floating around. It would be nice to have a standard way of doing this for people that need to be able to work backwards from the image to what it was built with. 45903 1 kergoth 2014-09-26 17:42:54 +0000 I'd definitely be interesting in steps in this direction. Having a way to identify the rootfs in some way would definitely be useful. I'd be interested in capturing not just layer information but *configuration* as well. 45904 2 2145 doug.geiger 2014-09-26 17:54:17 +0000 Created attachment 2145 build_info.inc I've attached a build_info.inc that I have used on some of my images to include a build timestamp, and layer names/version info in /etc/build 45905 3 doug.geiger 2014-09-26 18:10:36 +0000 (In reply to comment #2) > Created attachment 2145 [details] > build_info.inc Credit: Marc Ferland posted a similar set of commands in 2012: https://lists.yoctoproject.org/pipermail/yocto/2012-October/010136.html 46328 4 alejandro.hernandez 2014-10-14 20:29:23 +0000 Ok, so I'll be implementing this as an IMAGE_FEATURE, and this is what I'm trying to achieve: /etc/build: ----------------------- Build Configuration: | ----------------------- DISTRO = poky DISTRO_VERSION = 1.7 BB_VERSION = 1.24.0 BUILD_SYS = x86_64-linux TARGET_SYS = x86_64-poky-linux MACHINE = qemux86-64 USER_CLASSES = buildstats image-mklibs image-prelink IMAGE_CLASSES = image_types IMAGE_FEATURES = debug-tweaks buildinfo IMAGE_LINGUAS = IMAGE_INSTALL = packagegroup-core-boot run-postinsts PACKAGE_EXCLUDE = ----------------------- Layer Revisions: | ----------------------- meta = hsalejandro/6770:ccf5a4d2342c4fd40e4e0b332ea7e34e0bf175d4 meta-yocto = hsalejandro/6770:ccf5a4d2342c4fd40e4e0b332ea7e34e0bf175d4 meta-yocto-bsp = hsalejandro/6770:ccf5a4d2342c4fd40e4e0b332ea7e34e0bf175d4 46639 5 philip 2014-10-29 10:36:52 +0000 A couple of questions: 1) Have you thought about adding the build hostname? 2) Will the layer info show if the build machine has un-committed changes? 46652 6 alejandro.hernandez 2014-10-29 18:29:10 +0000 1 - No, I hand't thought of that, but it'd be relatively easy to add its variable to the function. 2 - The layer info would show the latest commit checksum 46653 7 philip 2014-10-29 20:22:44 +0000 It would be good to show if the git repos are clean or dirty. One of the things we are worried about is knowing if the build had uncommitted work. 46658 8 sgw 2014-10-29 21:21:11 +0000 I would agree with the git dirty vs clean additional information, but I would be concerned about the possibility of information leakage including the build hostname 46903 9 alejandro.hernandez 2014-11-10 16:12:14 +0000 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=ed3e25379c22da57a829f323b9404dd240de2272 2145 2014-09-26 17:54:17 +0000 2014-09-26 17:54:17 +0000 build_info.inc build_info.inc text/plain 366 doug.geiger IyBJbmNsdWRlIGJ1aWxkL3ZlcnNpb24gaW5mbyBpbiBhbGwgaW1hZ2VzCmRlZiBwcmludF9sYXll cnNfdmVyc2lvbihkKToKICAgIGxheWVydGV4dCA9ICJDb25maWd1cmVkIG1ldGFkYXRhIGxheWVy czpcbiVzXG4iICUgJ1xuJy5qb2luKGdldF9sYXllcnNfYnJhbmNoX3JldihkKSkKICAgIHJldHVy biBsYXllcnRleHQKCklNQUdFX1BSRVBST0NFU1NfQ09NTUFORCArPSAicm9vdGZzX3VwZGF0ZV90 aW1lc3RhbXAgO1wKICAgICAgICAgICAgICAgICAgICAgICAgICAgICBlY2hvICcke0BwcmludF9s YXllcnNfdmVyc2lvbihkKX0nID4gJHtJTUFHRV9ST09URlN9L2V0Yy9idWlsZCA7XAogICAgICAg ICAgICAgICAgICAgICAgICAgICAgICIK