270aa6fcbd
This is an automated CL created by the recipe roller. This CL rolls
recipe changes from upstream projects (depot_tools) into this repository.
The build that created this CL was
https://ci.chromium.org/b/8803629303281130545
depot_tools:
|
||
|---|---|---|
| .. | ||
| cipd | ||
| config | ||
| recipe_modules/crosvm | ||
| recipes | ||
| .gitignore | ||
| README.md | ||
| README.recipes.md | ||
| recipes.py | ||
Luci Infrastructure
This directory contains the configuration and build recipes run by our luci infrastructure for CI and presubmit testing.
Note: Luci applies config and recipes changes asynchronously. Do not submit changes to this directory in the same commit as changes to other crosvm source.
Recipes
Recipe Documentation
A few links to relevant documentation needed to write recipes:
Luci also provides a User Guide and Walkthrough for getting started with recipes.
For writing tests, documentation can be found in the Recipe test API and Post Process API
Running recipe tests
Recipes must have 100% code coverage to have tests pass. Tests can be run with:
cd infra && ./recipes.py test run
Most tests execute a few example invocations, record the commands that would be executed and compare
them to the json files in *.expected. This allows developers to catch unwanted side-effects of
their changes.
To regenerate the expectation files, run:
cd infra && ./recipes.py test train
Then verify the git diff to make sure all changes to outcomes are intentional.
Testing recipes locally
We try to build our recipes to work well locally, so for example build_linux.py can be invoked in the recipe engine via:
cd infra && ./recipes.py run build_linux
When run locally, recipes that check out crosvm, will run against the current HEAD of the main branch.
The recipe will run in the local infra/.recipe_deps/recipe_engine/workdir directory and is
preserved between runs in the same way data is preserved on bots, so incremental builds or the use
of cached files can be tested.
Testing recipes on a bot (Googlers only)
Note: See internal crosvm/infra documentation on access control.
Some things cannot be tested locally and need to be run on one of our build bots. This can be done with the led tool.
To test changes to an existing recipe, you need to find a previous build that you want to use as a template and get it's buildbucket id:
Then git commit your recipe changes locally and run:
led get-build $BBID | led edit-recipe-bundle | led launch
get-build will download and output the job definition, led edit-recipe-bundle will upload a
version of your local recipes and update the job definition to use them. The resulting job
definition can then be launched on a bot via led launch.