cbuild is the custom continuous integration system used by the toolchain group to build, test, and benchmark Linaro GCC, GDB, and QEMU.
https://launchpad.net/cbuild - Project on Launchpad
https://code.launchpad.net/cbuild - Source
https://code.launchpad.net/~linaro-toolchain-dev/cbuild/hardware - Machine descriptions
https://launchpad.net/tcwg-web - web frontend
https://code.launchpad.net/~linaro-toolchain-dev/cbuild/tools - More scripts.
http://ex.seabright.co.nz/helpers/scheduler - Older scheduler hosted by Michael Hope, now redirects to cbuild.validation.linaro.org
http://cbuild.validation.linaro.org/build/ - Raw build results
Since 2013-03, LAVA can be used as a backend for running cbuild jobs. LAVA is used as "dumb" backend only, essentially allowing to use LAVA board pool instead of dedicated cbuild board pool (and thus potentially improving capacity, especially if cbuild pool is merged into LAVA's). Further leveraging of LAVA capabilities, like detail test logs recorded in LAVA is possible and expected. To schedule a job to LAVA, it should be spawned into "lava-pandaes-usbdrive" queue, gcc daily builds are spawned into the queue automatically. Unfortunately, as of 2013-03, LAVA itself has low capacity of Panda ES boards which is the only validated board type for cbuild. So, the system can't yet be used to its full potential.
Note: To workaround capacity problem described above for infrastructure testing, there's number of other "lava-*" queues available. Using them does *not* produce valid builds, and will likely lead to build errors right away.
WorkingGroups/ToolChain/CBuild (last modified 2013-05-24 15:04:20)