| commit | d0f4f80818647cc84a836e2caa3dfbac4e28ea64 | [log] [tgz] |
|---|---|---|
| author | Andrii Shyshkalov <tandrii@chromium.org> | Thu Jan 10 03:25:55 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu Jan 10 03:25:55 2019 |
| tree | 7c0c3a395d93a58dca07eb27e899c07dd0c20ac6 | |
| parent | 844a3eb30c85cc64f5b620dd96a787df9e40769a [diff] |
Revert "Remove engine_flags from everywhere." This reverts commit 844a3eb30c85cc64f5b620dd96a787df9e40769a. Reason for revert: broke almost everything https://crbug.com/920497 Original change's description: > Remove engine_flags from everywhere. > > This also simplifies common_args, since the only 'operational-args' still > in use are used for the `run` subcommand. > > R=​martiniss@chromium.org > > Change-Id: I22aa494d714349475b5de3a58a1a7d68f622e28c > Bug: 646142 > Reviewed-on: https://chromium-review.googlesource.com/c/1403995 > Reviewed-by: Stephen Martinis <martiniss@chromium.org> > Commit-Queue: Robbie Iannucci <iannucci@chromium.org> TBR=iannucci@chromium.org,martiniss@chromium.org Change-Id: I747889a73be1262ec4e009cf1d7db99cb7d5ea1c No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 646142 Reviewed-on: https://chromium-review.googlesource.com/c/1404674 Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@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.package.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; depgraph, 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.