For a release (major/minor/point/milestone and uninative) we need to ferret out various revisions of tools and sources used by, or associated with, a given build, such as the hashes for poky, eclipse plugins, meta-qt*, and oe-core, etc.

For yocto-* releases, these are currently gleaned by the release scripts from filenames in the build directory. For uninative, that is not so easy to script since we need to know what rev of oe-core to tag, but it is not actively checked out and used by the actual build. That requires us to hunt logs in the AB UI, hoping to identify the correct build, to find the appropriate version to tag. We cannot snag that from the build worker build directory logs since subsequent builds would clobber. 

This is obviously time consuming and error prone for uninative. While we can accurately identify revs by the scripts for RCs, this should be something we capture as part of the build. It would have value apart from releases, too.