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