mirrors/crosvm
1
0
Fork 0
mirror of https://chromium.googlesource.com/crosvm/crosvm synced 2025-02-06 02:25:23 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
crosvm/infra
History
Dennis Kempin 5e7c6b1ab8 infra: Add email notifications for postsubmit and infra 
Both only notify myself for now as the luci infra is not
launched yet.

BUG=None
TEST=None

Change-Id: I4794bb118f6c27f145af9027ec317da2fb578af7
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3739370
Tested-by: kokoro <noreply+kokoro@google.com>
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-07-07 21:08:19 +00:00
..
cipd infra: Add build_windows recipe 2022-07-01 20:11:59 +00:00
config infra: Add email notifications for postsubmit and infra 2022-07-07 21:08:19 +00:00
recipe_modules/crosvm dev_container: Allow cargo home to be cached between runs 2022-07-07 17:49:47 +00:00
recipes infra: Use latest version of github secret 2022-07-07 20:26:46 +00:00
.gitignore
README.md infra: Add a little documentation about testing recipes 2022-06-03 18:36:40 +00:00
README.recipes.md Add crosvm_linux_x86_64_direct builder 2022-07-07 17:48:49 +00:00
recipes.py

README.md

WIP Luci Infrastructure

This directory contains the configuration and build recipes run by our luci infrastructure for CI and presubmit testing. This is currently a work in progress.

See Kokoro configs for the actively used presubmit system.

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.

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:

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.