= 768" x-on:close-sidebar="sidebar=window.innerWidth >= 768 && true">
Scheduling and executing shell jobs
Install
copied = false, 2000)"
:class="{ 'border-gray-700': !copied, 'text-gray-100': !copied, 'focus:ring-orange-500': !copied, 'focus:border-orange-500': !copied, 'border-green-600': copied, 'text-green-600': copied, 'focus:ring-green-500': copied, 'focus:border-green-500': copied }">
Authors
Maintainers
Sources
builder-0.3.0.tbz
sha256=0e823f6ab0084ab21f4ee44ca2f2aa7d001d3d55970cab58791fbc13022691ea
sha512=9d7359402eafd997db0b6b71ba49e49961d554c706717632d75f611924ab1cfa9f4ecd11a4a89adc46d3cce0b49c64bba360462be3e3a6694f4e64fce07d27fd
Description
The builder server has a schedule of jobs to be executed, stored persistently on disk. Any number of workers can connect via TCP (using ASN.1 encoded messages) that execute a single job -- usually contained in a sandbox (FreeBSD jail or Docker container). A client is a command-line interface to modify the schedule. Access control is out of scope - run it locally on your build host. The server receives the output artifacts of each job, and either stores them on the local file system or upload them to a remote server via http.
See https://builds.robur.coop for the live web frontend (builder-web).