The builder runs as a post-submit and will force push changes to github. Authentication is done via an access token stored in gcloud secrets manager. For this to work in the bot pool, the bots need to be reconfigured to receive the scope needed for access to the secrets API as done in https://crrev.com/i/4782519 Once this bot is working, the kokoro one can be turned off. Since we mirror from platform/crosvm to the new repo, luci is triggered for all new changes. BUG=b:233913820 TEST=./recipe.py run push_to_github Change-Id: I45478a076b87767ec10f0d0148c0713da7656264 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3671131 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
8.4 KiB
Repo documentation for crosvm
Table of Contents
- crosvm (Python3 ✅)
- build_chromeos (Python3 ✅)
- build_linux (Python3 ✅)
- crosvm:examples/build_context (Python3 ✅)
- crosvm:examples/prepare_source (Python3 ✅)
- health_check (Python3 ✅)
- push_to_github (Python3 ✅)
Recipe Modules
recipe_modules / crosvm
DEPS: depot_tools/bot_update, depot_tools/gclient, depot_tools/git, 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.
— def build_context(self, source=True, container=True):
Prepares everything needed to build crosvm on the revision that needs to be verified.
This updates the cwd to the crosvm source directory, ensures the revision to be tested is checked out and the dev container is ready.
Usage: with api.crosvm.build_context(): api.crosvm.step_in_container("build crosvm", ["cargo build"])
@property
— def builder_dir(self):
— def prepare_container(self):
— def prepare_git(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_chromeos
DEPS: crosvm, depot_tools/depot_tools, recipe_engine/buildbucket, recipe_engine/context, recipe_engine/file, recipe_engine/path, recipe_engine/properties, recipe_engine/step
PYTHON_VERSION_COMPATIBILITY: PY3
— def BuildAndTest(api, board):
— def CleanUp(api):
— def PrepareBuild(api):
— def RunSteps(api, properties):
— def SetupSource(api, workspace):
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/build_context
PYTHON_VERSION_COMPATIBILITY: PY3
— def RunSteps(api):
recipes / crosvm:examples/prepare_source
DEPS: crosvm, recipe_engine/buildbucket
PYTHON_VERSION_COMPATIBILITY: PY3
— def RunSteps(api):
recipes / health_check
DEPS: crosvm, recipe_engine/buildbucket, recipe_engine/context, recipe_engine/properties, recipe_engine/step
PYTHON_VERSION_COMPATIBILITY: PY3
— def RunSteps(api):
recipes / push_to_github
DEPS: crosvm, recipe_engine/buildbucket, recipe_engine/context, recipe_engine/file, recipe_engine/path, recipe_engine/raw_io, recipe_engine/step
PYTHON_VERSION_COMPATIBILITY: PY3
— def RunSteps(api):