Currently, we have md5sums generated by the MakeMD5Sums step and published with image artifacts via PublishArtifacts. So, an assumption is being made that that step is being run, even though it is not required. We need to pull md5sum publishing out of image publishing, create a new artifact publish block and actually publish md5sums in their own artifact block. I wouldn't be opposed to stripping that functionality into a new buildstep entirely, to be perfectly honest. Needed: - Strip md5sum publishing out of image artifacts in PublishArtifacts - Do magic stuff (fix it) - Fix any buildset-config that calls MakeMD5Sums
Relevant files: /lib/python2.7/site-packages/autobuilder/buildsteps/MakeImageMD5s.py /lib/python2.7/site-packages/autobuilder/buildsteps/PublishArtifacts.py Recent commits: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/commit/?id=94aa8d3de3af79dcf8055370139f18047d25c3ff
Yes, that commit was to fix the "Whoops. No tmp/deploy/images dir. I know, let's md5sum the entire build dir!" (BAD!) It shouldn't really effect this. Essentially if you look at how PublishArtifacts is called in buildset-config.master/* we should have like an 'md5sum' addition to it.
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/commit/?id=d7f48abdf3b178ca1f86cdbb2f85eb0cedde6571