commit | 90c7e6503a4950cb84a57b909bac36dd9eec595f | [log] [tgz] |
---|---|---|
author | Sergiy Belozorov <sergiyb@chromium.org> | Thu May 09 22:15:02 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Thu May 09 22:15:02 2019 |
tree | e3190b51bb81004ff9b08e8c394ae1099e8d5635 | |
parent | 5a39fa23e6c9a2dcb570f8442da6fb0cd3874a92 [diff] |
Display scheduler input request as a log to avoid flooding the build page E.g. https://ci.chromium.org/p/v8/builders/ci/V8%20Linux64%20-%20builder/41195 will become much less cluttered if the entire JSON on the "trigger" step was hidden behind a link. R=tandrii@chromium.org Recipe-Nontrivial-Roll: build Recipe-Nontrivial-Roll: build_limited_scripts_slave Recipe-Nontrivial-Roll: infra Change-Id: Ia2614ec7607bdbf0a3f1b738c46e057ddc54862c Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1599574 Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org>
Recipes are a domain-specific language (embedded in python) for specifying sequences of subprocess calls in a cross-platform and testable way.
README.md
This file!
doc/
Documentation for the recipe engine (including this file!). See the design doc for more detailed design information about the recipe engine.
infra/
Chrome infra config files.
recipes.py
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/
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)
recipe_modules/
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.
recipe_engine/
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 recipes.cfg
file.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; run
, and autoroll
are some examples.
unittests/
Somewhat poorly named, these are higher level integration tests.
user.email
and user.name
are configured in git config
.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 joe@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.
Use git cl help
and git cl help <cmd>
for more details.