tinderbox


I run a build bot to identify build + install issues of Gentoo Linux software packages*.

Currently 8 chroot images are running in parallel at dedicated server (i7-3930, 12 cores, 64 GB RAM, 2x 3 TB HDD). Each image is set up from a recent stage3 with an arbitrary combination of (~)amd64 + profile + USE flag set.

Within each image all packages will be tried to be emerged in a randomized order. The repository at the host is shared to all images and synced every 3 hours. Added or modified packages are put on top of each work queue. Once a day @system is tried to be updated in each image. No parallel make, no parallel emerge and no unmerge are made.

About 700 packages per image are emerged daily, <2.5% do fail. The calculated coverage of the repository is 85% after 7 days with 8 running images.

An image is replaced by a fresh new one usually after 12-17 days (based on this model). The old image is kept around for few weeks.

The Portage File List is fed too. Github hosts the source code.

*just to have fun, but to redeem too to a Linux distribution I do use and trust since 2003. The Gentoo project has its own tinderbox cluster with a slightly different approach.


tl;dr;
The tinderbox runs in each chroot: "qsearch --all | sort --random-sort | xargs -n 1 emerge --update" and just parses the output.


back to my home page