This allows us to run multiple steps with the same intermediate build data. To make sure we start with a clean slate, any existing containers are deleted at the beginning of each recipe. BUG=b:233913455 TEST=./recipes.py test run Change-Id: Ieda684d40bf08937183cba34242360c025724af8 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3668813 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
4.9 KiB
Repo documentation for crosvm
Table of Contents
- crosvm (Python3 ✅)
- build_linux (Python3 ✅)
- crosvm:examples/container (Python3 ✅)
- crosvm:examples/prepare_source (Python3 ✅)
Recipe Modules
recipe_modules / crosvm
DEPS: depot_tools/bot_update, depot_tools/gclient, recipe_engine/buildbucket, recipe_engine/context, recipe_engine/file, recipe_engine/path, recipe_engine/step
PYTHON_VERSION_COMPATIBILITY: PY3
class CrosvmApi(RecipeApi):
Crosvm specific functionality shared between recipes.
@property
— def builder_dir(self):
— def prepare_container(self):
— def prepare_source(self):
Prepares the local crosvm source for testing in self.source_dir
CI jobs will check out the revision to be tested, try jobs will check out the gerrit change to be tested.
@property
— def source_dir(self):
— def step_in_container(self, step_name, command):
Runs a luci step inside the crosvm dev container.
Recipes
recipes / build_linux
DEPS: crosvm, recipe_engine/buildbucket, recipe_engine/context, recipe_engine/properties, recipe_engine/step
PYTHON_VERSION_COMPATIBILITY: PY3
— def RunSteps(api, properties):
— def get_test_args(api, test_arch):
Returns architecture specific arguments for ./tools/run_tests
recipes / crosvm:examples/container
PYTHON_VERSION_COMPATIBILITY: PY3
— def RunSteps(api):
recipes / crosvm:examples/prepare_source
DEPS: crosvm, recipe_engine/buildbucket
PYTHON_VERSION_COMPATIBILITY: PY3
— def RunSteps(api):