June 19 2016 2:11 AM, "Adrien Destugues" <pulkomandy@xxxxxxxxxxxxx> wrote:
On Sun, Jun 19, 2016 at 04:13:06AM +0000, Alexander von Gluck IV wrote:
I worked on getting the haikuporter build-master installed in a public VM
tonight and
ran in to quite a few concerns about it. The number one issue I saw was the
requirement
that each Haiku build-slaves be accessible via IP + SSH
Given these machines generally run behind user NAT's, and is "single-shot" I
think the
haikuporter build-master might be *too* simplistic.
We've collected up quite a few package builders now. Here is my personal
analysis.
I'm trying to remain independent and honest in my list given I have a horse
in the race
(and old, un-maintained one)
I think we're all assuming haikuporter build-master is a lot more magic than
it actually
is. Some great work has been put into it, but I want to make sure there is
consensus
that haikuporter build-master is the way to go.
https://github.com/waddlesplash/haiku-kitchen
haiku-kitchen (waddlesplash)
Pro
- Runs as a service
I don't understand why this is a "pro"?
- IRC client
Our IRC channels are getting quite noisy with many notification bots.
Are we sure we want even more of that?
https://github.com/haikuports/haikuporter
haikuporter build-master mode (mmlr)
Cons
- SSH's out to slaves and requires user to open ssh port per slave. (and
static ip)
Reverse-SSH can be used, IIRC.
- *Basic* html report of each single-shot run.
... but conveniently exports a JSON file with all the required data to
build or plug a better one (possibly some code from the other projects
could be reused here?).
This sounds more like a Pro to me, it means we can leave the core server
untouched and toy around with the web interface. Or we could write a
native Haiku app or whatever. Modularity is good.
- Single shot for one package (or a bunch? --do-bootstrap seems broken here)
and deps
Which is what we need to trigger it as a git post-commit hook (on all
changed recipes). I still don't get the idea that this should be an
external service
This sounds more like a Pro to me, it means we can leave the core server
untouched and toy around with the web interface. Or we could write a
native Haiku app or whatever. Modularity is good.
- Poor documentation (I've written whats out there now)
And mmlr sent mails to our mailing lists describing things a bit. That's
not documentation, but it could be turned into some.