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.10.0"}
11 "dune" {>= "2.0.0"}
12 "asn1-combinators" {< "0.3.0"}
13 "bheap" {>= "2.0.0"}
14 "bos"
15 "cmdliner"
16 "cstruct" {>= "6.0.0"}
17 "duration"
18 "fmt"
19 "fpath"
20 "logs"
21 "lwt"
22 "ptime"
23 "rresult"
24 "uuidm"
25 "http-lwt-client" {>= "0.0.2" & < "0.1.0"}
26 "base64"
27]
28build: [
29 ["dune" "subst"] {dev}
30 ["dune" "build" "-p" name "-j" jobs]
31 ["sh" "-ex" "packaging/FreeBSD/create_package.sh"] {os = "freebsd"}
32 ["sh" "-ex" "packaging/debian/create_package.sh"] {os-family = "debian"}
33]
34
35synopsis: "Scheduling and executing shell jobs"
36description: """
37The builder server has a schedule of jobs to be executed, stored persistently
38on disk. Any number of workers can connect via TCP (using ASN.1 encoded
39messages) that execute a single job -- usually contained in a sandbox (FreeBSD
40jail or Docker container). A client is a command-line interface to modify the
41schedule. Access control is out of scope - run it locally on your build host.
42The server receives the output artifacts of each job, and either stores them
43on the local file system or upload them to a remote server via http.
44
45See https://builds.robur.coop for the live web frontend (builder-web).
46"""
47url {
48 src:
49 "https://github.com/robur-coop/builder/releases/download/v0.1.0/builder-v0.1.0.tbz"
50 checksum: [
51 "sha256=a13174ec52d1e5163ba441de2039d1e87c16f1b8962af535c85df454995c7cac"
52 "sha512=21b2773be22ea6f4561c8e8e43623ba1e85299c27d6e2a3631c69cd8d2936eb15dbc6e8a4b58daa27a29f019951c2df1506e19042664bfa9987b551f89ff81ec"
53 ]
54}
55x-commit-hash: "1c0821325452cc1bd0fefdcb718a694682efea82"