The autobuilder produces buildhistory output: https://git.yoctoproject.org/cgit/cgit.cgi/poky-buildhistory/ We should set up the buildhistory-web tool to analyse and report on this output: https://git.yoctoproject.org/cgit/cgit.cgi/buildhistory-web/ I expect this is going to lead to some enhancements to buildhistory-web and the analysis code (meta/lib/oe/buildhistory_analysis.py), since this hasn't seen much testing in anger yet (apart from local usage of the buildhistory-diff command line tool).
Looking at this it seems like buildhistory-web needs to support the multi-branch buildhistory repository that we use so that we can get the buildhistory for all the builds we collect it for.
We've got the automation of buildhistory-web data importation going: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/commit/?id=c12baee716458846e3f2102fe5e89ba363559b00 We still seem to be having some issues with the apache config on this. I'm guessing this will get fixed in a day or so, but as for now, we've finally got some movement on this.
We're going to need the machine on the new cluster for this. Michael, per our discussion.
There is a copy up at http://history.yoctoproject.org/warningmgr/. It's currently reimporting the data from git://git.yoctoproject.org/poky-buildhistory. I'm still working on improving performance of the deployment. The new data coming in from the autobuilder is currently only for master builds. We will need to do some work to track other builds (mut, krogoth-next, etc.) as needed.
http://history.yoctoproject.org/warningmgr/ is getting updates. We may need a new ticket to add the tracking of builds on other branches.