You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,6 +55,23 @@ Add a new image to [`config.yaml`](./config.yaml) file and it will be built on s
55
55
dockerfile: ./lighthouse/Dockerfile # optional docker file to use, defaults to the source repository's Dockerfile
56
56
```
57
57
58
+
## `branches.yaml` syntax
59
+
60
+
`config.yaml`is generated from `branches.yaml` by `generate_config.py`. Each client lists branches that should be built; the branch name is used directly as the docker tag (slashes become hyphens).
61
+
62
+
To build from one branch but publish under a different tag, use `<branch>:<tag>`:
63
+
64
+
```yaml
65
+
teku:
66
+
branches:
67
+
- master
68
+
- prototype/focil:focil # builds prototype/focil, publishes as :focil
69
+
```
70
+
71
+
The same syntax works inside `alt_repos` entries (the alt-repo prefix is still prepended to the override tag).
72
+
73
+
After editing `branches.yaml`, run `python3 generate_config.py` to regenerate `config.yaml`.
74
+
58
75
## Per-tag Dockerfile convention
59
76
60
77
When a build needs a different Dockerfile than the default (e.g. an alt-fork branch that doesn't work with the upstream one), drop it in alongside the default using the naming convention:
0 commit comments