On Sun, Nov 29, 2015 at 12:45:16PM +0100, Michael Lotz wrote:
The setup I've gone for requires the system to be fully self contained. It
requires that all dependencies (including the Haiku packages themselves) are
provided to the system and there are no implicit provides in some list that
needs to be maintained. It will also distribute all of these dependency
packages to the builders and enforce that no system packages of the build
host are used. This ensures that the packages will always be consistent and
no packages that just happen to be installed on one of the build hosts can
"leak" into the result and introduce subtle differences (i.e. resolved
requires in the packages pointing to different versions than was expected).
This is IMO a desirable property and goes beyond just build scheduling.
I can spend some more time on this to implement HPKR generation which would
then essentially make the system complete. It will not have a fancy web
frontend as the other two approaches have. That is IMHO not all that
important for an automated build. It produces logs that could easily be
exposed via a standard web server to produce something similar to what
buildbot exposes. It doesn't really make sense to spend this time if noone
else sees merit in the essence of my approach. Comments on that would
therefore be appreciated.
