mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2025-02-10 12:09:31 +00:00
Mingw64 builds are used frequently by linux developers to check windows portions of crosvm and part of ./tools/presubmit. Test in postsubmit and once the builder is green it can be enabled in the CQ as well. BUG=b:254316054 TEST=recipes.py tests run Change-Id: I8495446772a54d63644e73d07423892e28cedd1a Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3964541 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com> |
||
---|---|---|
.. | ||
generated | ||
main.star | ||
README.md | ||
recipes.cfg |
LUCI config
This directory contains LUCI configuration.
Directory structure
main.star
: The high-level LUCI configuration given as a Starlark script. By processing this file with lucicfg, low-level *.cfg will be generated under./generated/
.generated/
: The directory containing *.cfg generated frommain.star
.recipes.cfg
: The file defining the dependencies for our recipes such as modules. Whenever those dependencies are updated the Recipe Roller bot will update this file with the latest revision hashes.
Making changes
- Modify the
main.star
- Run
./main.star
. Then, cfg file(s) ingenerated/
are updated. - Run
lucicfg validate main.star
. This will send the config to LUCI to verify the generated config is valid.