On Sun, Jun 19, 2016 at 3:15 PM, Alexander von Gluck IV
<kallisti5@xxxxxxxxxxx> wrote:
Reverse-SSH can be used, IIRC.
I can't find any documentation, arguments, or code on this... it seems this
should be
the default behavior for the outlines reasons. (Since we need one complete
haikuporter
build-master per architecture, how would this even work?)
- *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.
I'm all about microservices, but my main concern is this whole thing sounds
like it is going to be held together via 30 cron jobs, 10 scripts in
/usr/local/bin,
and a few old men to log in and manually fix stuff every other day.
- 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.
The thing is single shot anyway and we'll have to run a complete instance for
each
architecture... so I fail to see the "leave core alone" argument.
The git trigger is a good point. I didn't think about it from that
perspective.
- 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.
Example? I've spent a bit of time searching ML threads and can't find any
details or example usage.
