|author||Garrett Beaty <firstname.lastname@example.org>||Tue Apr 23 22:11:39 2019|
|committer||Commit Bot <email@example.com>||Tue Apr 23 22:11:39 2019|
Update post_process_test.py to call magic_check_fn.post_process. Manually constructing a checker and invoking post process hooks requires changes to the test whenever the arguments for the checker or the types expected to be passed to a hook change. Using post_process instead limits the amount of changes that require updating all of the tests in post_process_test.py to only those that change the public interface of the magic_check_fn module. Change-Id: I66f60cacf5be735cb8d525f5c3fdfc5e7d41c901 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1577825 Auto-Submit: Garrett Beaty <firstname.lastname@example.org> Reviewed-by: Robbie Iannucci <email@example.com> Commit-Queue: Robbie Iannucci <firstname.lastname@example.org>
Recipes are a domain-specific language (embedded in python) for specifying sequences of subprocess calls in a cross-platform and testable way.
Documentation for the recipe engine (including this file!). See the design doc for more detailed design information about the recipe engine.
Chrome infra config files.
The main entry point to the recipe engine. It has many subcommands and flags; run
recipes.py -h to see them. Include this in your repository to start using recipes.
Recipes in the recipe engine. These are either example recipes, or recipes which are used to test the engine (see run_test.py to see these run)
Built in recipe modules. These are very useful when writing recipes; take a look in there, and look at each of their
examples subfolders to get an idea how to use them in a recipe.
The core functionality of the recipe engine. Noteworthy files include:
main.py-- The main entrypoint for the recipe engine.
recipes_cfg.proto-- The protobuf file which defines the format of a
third_party/-- third_party code which is vendored into the recipe engine.
recipe_api.py-- The api exposed to a recipe module.
unittests-- Unittests for the engine.
There are also several files which correspond to a subcommand of recipes.py;
autoroll are some examples.
Somewhat poorly named, these are higher level integration tests.
user.nameare configured in
Run the following to setup the code review tool and create your first review:
git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git $HOME/src/depot_tools export PATH="$PATH:$HOME/src/depot_tools" git checkout -b work origin/master # hack hack git commit -a -m "This is awesome" # This will ask for your Google Account credentials. git cl upload -s -r email@example.com # Wait for approval over email. # Click "Submit to CQ" button or ask reviewer to do it for you. # Wait for the change to be tested and landed automatically.
git cl help and
git cl help <cmd> for more details.