Chromium OS infrastructure recipes (

Clone this repo:


  1. f8bb3dd Don't build image when performing FindIt bisect build. by David Burger · 2 days ago master
  2. 5827edf Refactor orchestrator and add test logic. by Yaakov Shaul · 4 days ago
  3. 4aaafbd Temporarily schedule subset of children. by Andrew Lamb · 4 days ago
  4. f087055 Add FindIt package processing to build_target recipe. by David Burger · 4 days ago
  5. 94129fe Schedule postsubmit build for all builders in BuilderConfigs. by Andrew Lamb · 5 days ago

Chrome OS Recipes

This is a quick-start guide for Chrome OS Recipes. For more in-depth information about the Recipes framework, see the Recipes User Guide.

The recipes and recipe modules in this repo have documentation auto-generated by the ‘test train’ process:

Getting Started

The script in this repo will bootstrap itself. You can verify that it is working by running tests:

./ test run

After making a change, you will usually need to “re-train” expected output in order for tests to pass:

./ test train

This will also regenerate the documentation. That file and the expectation data in *.expected directories should be checked in with your changes.

Support Tools

This repo contains some non-recipes support tooling in the support/ directory. These tools are delivered to CI hosts via CIPD. This process is automated by the support/ script. See support/README.txt for more details.

Chrome OS Recipes Code Style

  • The Python code in this repo should largely conform to Chromium Python style except that Recipes code has a convention of 2 space indents. Practically, we use YAPF for automatic code formatting; whatever style is generated by YAPF should be used.

  • The code in this repo uses docstring-based type annotations as implemented by the Sphinx Napoleon Plugin. This format is supported by PyCharm / IntelliJ (Settings > Tools > Python Integrated Tools > Docstring format > Google).

  • The Recipes framework does not require the RecipesApi subclass in recipe modules to have any particular name, but this repo has some tooling that expects it to be named NameApi derived from the recipe_modules/<name>/.