Hello,
As a heads-up for CBuild/LAVA integration project, http://ec2-54-243-13-36.compute-1.amazonaws.com/helpers/scheduler is now available, which has initial(?) web frontend integration with LAVA. That page (currently) shows job "gcc-linaro-4.6-2012.09.job", submitted against queue "lava-panda-mock", with a link to latest build in LAVA (extra feature, I couldn't find a way in CBuild frontend to get to native build results).
If you want to try it yourself, it's accessible to same TCWG people as http://cbuild.validation.linaro.org/ , plus me, Stevan, and Danilo. So, if you're not in list, please drop us a line. "Spawn" and "Bump up" actions support integration with LAVA currently. We're in the process of identifying what other features of web frontend would require LAVA integration, hints from TCWG are appreciated.
Now a bit about architecture. We're targetting to support both native CBuild and LAVA schedulers. This is per-queue, i.e. one queue can use native scheduler and another LAVA. LAVA is detected by the presence of LAVA job definition template file in a scheduler queue dir: http://bazaar.launchpad.net/~linaro-infrastructure/cbuild/cbuild-scheduler_c... lava-test-shell script with actual commands to run for build is also served by CBuild frontend based on a template in that dir.
Currently, sandbox defines 3 test queue for LAVA integration:
lava-panda - build something on panda (tested only with gcc, needs more work)
lava-panda-mock - doesn't really compiles stuff, just downloads snapshot of previous gcc build. This allows for quicker (~15min) turnaround during testing, if you test snadbox, please use this queue.
lava-qemu-mininal - for local development with even shorter turnaround, won't work on sandbox.
If you have any feedback on the architecture above, please share it. Otherwise, we're proceeding to support it in cbuild-tools.