This is *not* a public build service: it will only expose the analysis functionality, using information from the Autobuilder builds. It is important we don't break the Autobuilder while trying to integrate it with Toaster, so Alex has suggested we start by using the Autobuilder instance in Romania. If that doesn't break, we can then move to the "real" Autobuilder. Richard observed that right after the release is the best time for playing Autobuilder-related games, so ideally this would need to happen during M1.
I've designed a 2-phase approach: 1. Build the solution and demonstrate it on the Romania AutoBuilder/Toaster interface with private (Intel-only) access. The deliverables are: autobuilder code, toaster code and documentation for installation. 2. Deployment on the public Autobuilder with public Toaster access. The kickoff for 1. has taken place. Will follow up on this bug when phase 1. deliverables are completed.
The needed patchsets for Autobuilder have been merged. A timeline for setting up the Toaster server and enabling the service on the Autobuilder is not clear.
This is now available at http://toaster-ab-dev.yoctoproject.org/ Thanks to all involved for making this happen.