this repo has no description
1opam-version: "2.0"
2maintainer: "Robur <team@robur.coop>"
3authors: ["Robur <team@robur.coop>"]
4homepage: "https://github.com/robur-coop/builder"
5dev-repo: "git+https://github.com/robur-coop/builder.git"
6bug-reports: "https://github.com/robur-coop/builder/issues"
7license: "ISC"
8
9depends: [
10 "ocaml" {>= "4.08.0"}
11 "dune" {>= "2.0.0"}
12 "asn1-combinators" {< "0.3.0"}
13 "bheap" {>= "2.0.0"}
14 "bos"
15 "cmdliner" {>= "1.1.0"}
16 "cstruct" {>= "6.0.0"}
17 "duration"
18 "fmt" {>= "0.8.7"}
19 "fpath"
20 "logs"
21 "lwt"
22 "ptime"
23 "uuidm"
24 "http-lwt-client" {>= "0.2.0"}
25 "base64"
26]
27build: [
28 ["dune" "subst"] {dev}
29 ["dune" "build" "-p" name "-j" jobs]
30 ["sh" "-ex" "packaging/FreeBSD/create_package.sh"] {os = "freebsd"}
31 ["sh" "-ex" "packaging/debian/create_package.sh"] {os-family = "debian"}
32]
33
34synopsis: "Scheduling and executing shell jobs"
35description: """
36The builder server has a schedule of jobs to be executed, stored persistently
37on disk. Any number of workers can connect via TCP (using ASN.1 encoded
38messages) that execute a single job -- usually contained in a sandbox (FreeBSD
39jail or Docker container). A client is a command-line interface to modify the
40schedule. Access control is out of scope - run it locally on your build host.
41The server receives the output artifacts of each job, and either stores them
42on the local file system or upload them to a remote server via http.
43
44See https://builds.robur.coop for the live web frontend (builder-web).
45"""
46url {
47 src:
48 "https://github.com/robur-coop/builder/releases/download/v0.3.2/builder-0.3.2.tbz"
49 checksum: [
50 "sha256=e769117348ae2f425018c24137ecb1de8ffbadd11f9f027bce299f556b60f530"
51 "sha512=f8cdb6c3f6684a97799e6f6b6a4f20c7b1632bca5a9ddbe0c9862c6bc85c0994b53102425afd4edf356169603d3701e584554be8069b9407b58404e5613cd445"
52 ]
53}
54x-commit-hash: "afd7e760a3341aa713cd17ed5573a899b9df728c"