May 20 2016 2:05 AM, "PulkoMandy" wrote:
I think a community member that want to contribute should begin to use
haikuporter, build packages and report problems.
That is the part which is automated by mmlr build system.
As far as I know, the main problems are:
- Once the build system is up and running (or using the current version hosted
by mmlr), the result of the automated builds should be reviewed, and all issues
found should be fixed. You can already have a look at the build reports from
the build system, but I think there is not yet an easy to read "status report".
Maybe we could plug waddlesplash's web interface for this onto the new build
system, or maybe we should write a new web interface from scratch. Until then,
some manual parsing of the build report is required.
When I spoke to mmlr, it seemed he didn't have much interest in making a web
interface. (speak up mmlr if i'm wrong)
Is there a python expert out there who would be interested in exposing a REST
api in haikuporter running in master mode?
get /api/recipes
get /api/buildslaves
get /api/builds
get /api/packages
get /api/log
etc. Making on-the-fly buildmaster changes (post) would be nice as well down
the road.
Having a RESTful control interface exposed in the master service would let
people make an interface in whatever language
they see fit. (crazy node.ns, ruby, more python, etc) :-) Hell, my rails
Haikeuken project could be modified to poll build status info
pretty easily.
What I know based on trying to stand it up on my own:
* haikuporter buildmaster runs on Linux
* haikuporter buildmaster ssh' out to remote Haiku build machines via a
pre-set keypair
If we want to get fancy, we could run the buildmaster on haiku hardware, and
have a few buildslaves in AWS.
I think the biggest limiting factor at the moment is man hours... we seem to
have a surplus of work
to do and a limited number of man hours available to do it.
-- Alex
