datakit/datakit-bridge-local-git.opam at master · moby/datakit · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
opam-version: "2.0"
maintainer: "thomas.leonard@docker.com"
authors: "Thomas Leonard"
license: "Apache"
homepage: "https://github.com/moby/datakit"
doc: "https://docker.github.io/datakit/"
bug-reports: "https://github.com/moby/datakit/issues"
depends: [
  "ocaml"
  "dune" {build}
  "cmdliner"
  "irmin-watcher"
  "irmin" {>= "1.2.0"}
  "irmin-unix" {>= "1.2.0"}
  "lwt" {>= "3.0.0"}
  "logs"
  "fmt"
  "protocol-9p-unix" {>= "0.11.0"}
  "datakit-client" {>= "0.12.0"}
  "datakit-client-9p" {>= "0.12.0"}
  "datakit-github" {>= "0.12.0"}
]
build: ["dune" "build" "-p" name "-j" jobs]
dev-repo: "git+https://github.com/moby/datakit.git"
synopsis: "DataKit Local-Git bridge"
description: """
This service is a drop-in replacement for the DataKit-GitHub bridge
that instead just monitors a local Git repository. It is useful for
testing a new DataKitCI configuration without having to configure
GitHub integration first.

The local bridge monitors the state of one or more local Git
repositories, writing the current head of each branch to
DataKit. DataKitCI can be configured to run the CI tests against the
project each time a commit is made.

Once you are happy with the way the CI is working, you can replace
this service with the GitHub bridge service to have the CI test a
project hosted on GitHub instead.

Unlike the GitHub bridge, this service:

- only reports on branches, not tags or pull requests;
- does not report build statuses from other CI systems; and
- does not push the statuses set by the CI anywhere.
"""