Stitch any CI into Tangled
update README
+33
-11
+33
-11
README.md
+33
-11
README.md
···
5
5
to Tangled using standard ATProto records so they show up natively
6
6
in Tangled's UI.
7
7
8
+
> [!WARNING]
9
+
>
10
+
> **Project status:** Tack is early and experimental software.
11
+
> This repo itself uses Tack and I (mitchellh) use Tack for my projects,
12
+
> but it is still new and relatively unproven.
13
+
8
14
## Example
9
15
10
16
A Tangled workflow that fires a Buildkite pipeline on every push to
···
17
23
branch: ["main"]
18
24
- event: ["pull_request"]
19
25
branch: ["main"]
26
+
27
+
# this does nothing for Tack but is required by Tangled
28
+
engine: nixery
20
29
21
30
tack:
22
31
buildkite:
···
42
51
status, counts, etc. can show up inline in things like pull requests.
43
52
44
53
```
45
-
sh.tangled.pipeline
46
-
Jetstream ───────────────────────▶ tack
47
-
│
48
-
│ Create Build
49
-
▼
50
-
Buildkite
51
-
│
52
-
│ webhooks
53
-
▼
54
-
tack ──── /events (WebSocket) ────▶ Tangled appview
55
-
sh.tangled.pipeline.status
54
+
Jetstream Knot /events (WebSocket)
55
+
sh.tangled.repo sh.tangled.pipeline triggers
56
+
sh.tangled.spindle.member
57
+
sh.tangled.repo.collaborator
58
+
│ │
59
+
│ (discover knots │
60
+
│ + membership) │
61
+
▼ ▼
62
+
╭────────────────────────────────╮
63
+
│ tack │
64
+
│ ╭──────────────────────────╮ │
65
+
│ │ provider router │ │ selected per-workflow
66
+
│ │ (fake │ buildkite) │ │ via `tack: { … }` YAML
67
+
│ ╰──────────────────────────╯ │
68
+
╰────────────────────────────────╯
69
+
│
70
+
│ Create Build (REST)
71
+
▼
72
+
Buildkite
73
+
│
74
+
│ POST /webhooks/buildkite
75
+
▼
76
+
tack ──── /events (WebSocket) ────▶ Tangled appview
77
+
sh.tangled.pipeline.status
56
78
```
57
79
58
80
## Configuration