Name Date Size #Lines LOC

..--

generated/H25-Apr-2025-887871

README.mdH A D25-Apr-20251.2 KiB2418

main.starH A D25-Apr-202510.7 KiB401327

recipes.cfgH A D25-Apr-2025951 3635

README.md

1# LUCI config
2
3This directory contains LUCI configuration.
4
5## Directory structure
6
7- [`main.star`](./main.star): The high-level LUCI configuration given as a
8  [Starlark](https://github.com/google/starlark-go) script. By processing this file with
9  [lucicfg](https://chromium.googlesource.com/infra/luci/luci-go/+/HEAD/lucicfg/README.md),
10  low-level \*.cfg will be generated under `./generated/`.
11- [`generated/`](./generated/): The directory containing \*.cfg generated from `main.star`.
12- [`recipes.cfg`](./recipes.cfg): The file defining the dependencies for our recipes such as
13  [modules](https://chromium.googlesource.com/chromium/tools/depot_tools.git/+/HEAD/recipes/README.recipes.md#Recipe-Modules).
14  Whenever those dependencies are updated the
15  [Recipe Roller bot](https://chromium-review.googlesource.com/q/project:crosvm/crosvm+owner:recipe-mega-autoroller%2540chops-service-accounts.iam.gserviceaccount.com)
16  will update this file with the latest revision hashes.
17
18## Making changes
19
201. Modify the `main.star`
211. Run `./main.star`. Then, cfg file(s) in `generated/` are updated.
221. Run `lucicfg validate main.star`. This will send the config to LUCI to verify the generated
23   config is valid.
24