oclusterversion

Distribute build jobs to workers

OCluster manages a pool of build workers. A build scheduler service accepts build jobs from clients and distributes them to worker machines using Cap'n Proto. Workers register themselves by connecting to the scheduler (and workers do not need to be able to accept incoming network connections).

The scheduler can manage multiple pools (e.g. linux-x86_64 and linux-arm32). Clients say which pool should handle their requests. At the moment, two build types are provided: building a Dockerfile, or building an OBuilder spec. In either case, the build may done in the context of some Git commit. The scheduler tries to schedule similar builds on the same machine, to benefit from caching.

AuthorsAntonin D├ęcimo <antonin@tarides.com>, David Allsopp <david.allsopp@metastack.com>, Kate <kit.ty.kate@disroot.org>, Lucas Pluvinage <lucas@tarides.com>, Mark Elvers <mark.elvers@tunbury.org>, Patrick Ferris <patrick@sirref.org>, Thomas Leonard <talex5@gmail.com> and Tim McGilchrist <timmcgil@gmail.com>
LicenseApache-2.0
Published
Homepagehttps://github.com/ocurrent/ocluster
Issue Trackerhttps://github.com/ocurrent/ocluster/issues
MaintainerTim McGilchrist <timmcgil@gmail.com>
Dependencies
Source [http] https://github.com/ocurrent/ocluster/releases/download/v0.3.0/ocluster-0.3.0.tbz
sha256=8879c113a6ec6a1d96bbda4e7f1e2f2cfba8f57630cdf715c770b3dc72628a96
sha512=74c42d68c2b741a6394913f1ef9af784f3bcfae164eb5e88d9d87d635032c52b4b0c196fb2bd9db8127dd5c1aff103baecc791d2c081df82275ef5c5cdec7c8a
Edithttps://github.com/ocaml/opam-repository/tree/master/packages/ocluster/ocluster.0.3.0/opam
No package is dependent