[haiku-development] Re: [RFC] Automated package builds: Proposed Architecture
- From: pulkomandy <pulkomandy@xxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 12 Sep 2014 20:10:14 +0200
On Fri, Sep 12, 2014 at 01:28:14PM -0400, Augustin Cavalier wrote:
> On Sep 12, 2014 1:13 PM, "pulkomandy" <pulkomandy@xxxxxxxxxxxxx> wrote:
> > Can't we just use buildbot? why would we need a custom NodeJS server
> > for this?
>
> The buildbot is more suited towards repeatedly building a single target as
> code changes are made. HaikuPorts is quite different: there are many
> targets that don't always need to be rebuilt when one change is made. If
> Buildbot can do this, that's great; but I haven't heard from Oliver that it
> can be done.
I'd say this is up to haikuporter. We'd need some command like
"haikuporter -S everything" to build all packages as needed. Things
already built will be in the ports/packages/ dir and won't be rebuilt.
If we don't use haikuporter dependency tracking, we will be duplicating
the dependency computation in another tool, which doesn't sound like a
good idea.
Moreover, we can still use buildbot to get the git repository watching,
web interface, IRC bots, and buildslave distribution. Redoing all of
this sounds like a major paste of time. Buildbot can then run any
command on the slaves once it notices something changed, and this is
where I think we should plug our build infrastructure, either a simple
haikuporter invocation or calling another tool if that's needed.
Previous attempt at a custom automated build for Haiku didn't work very
well. You can check the blog updates from that GSoC 2011 project:
https://www.haiku-os.org/blog/jrabbit
I think using buildbot as much as possible for what it does well sounds
like a better idea than doing the same from scratch.
--
Adrien.
Other related posts:
