Hi everyone, I'm developing (during my free time, which makes the progress a bit slow) a system for building Gentoo Packages in a distributed manner, to be specific as Open Build Service ( build.opensuse.org ) does - generic, but focused on Gentoo.
The Gentoo Build Service project will have as aim to provide a software and relative ebuilds that would offer a way to deploy privately a build service: A web interface that exposes API to control remote workers (a cluster of builders, so to say) that can build packages as a set of repo with specifications that indicates the packages and the desired customizations (useflags, keywords, local ebuilds override, ecc..). In such way, the webui can be hooked also to Github repositories, and build-test against Pull requests or changes of an overlay, and even the Gentoo tree, with the option to publish the generated artefacts thru the web server. Do not me wrong here, i know this can be seen as: 'why do not join effort to get Gentoo properly supported on Open build service?' I'm detaching a bit from the Open Build Service for one reason: the choice of technologies stack, which is radically and completely different. Currently the project is in really alpha/experimental state, and it lays on Github [2], for the moment it allows distributed build, with live stream report back to the master node. Agents (as build nodes) are communicating with a master central point thru AMQP, and basically all is written in Golang (hate or love it, imo it's the good choice for backend/API tasks). Development plan and goals will be updated to the Project page soon [1] What do you think about it? Best, Ettore 1: https://wiki.gentoo.org/wiki/Project:Build_Service
signature.asc
Description: OpenPGP digital signature
