tinderbox


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

Currently 7 chroot images are running in parallel at a dedicated server (i7-3930, 6 cores, 12 cpu, 64 GB RAM, 6 TB disk). Each image is set up from a recent stage3 tarball as an arbitrary combination of (~)amd64 + profile + USE flag set.

Within each image the packages of the main Gentoo tree are tried to be emerged in a randomized order. Once a day @system and @world are updated. No parallel make, no parallel emerge and no unmerge is made. The main repository is synced hourly by the host system and shared to all chroot images. Changed packages of the main repository are mixed into the backlog of each image.

600 packages per image are emerged daily, 2% do fail (4% with FEATURES=test). The coverage of the main repository is about 80% after a week.

An image is replaced by a fresh new one usually after 7 days (based on this model). At that time betwen 5,000 and 7,000 packages were emerged. The old image is kept around for 2-3 months.

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

*just to have fun, and to redeem 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