| commit | 68d2ac243180dbd51a1c3a672874d072235f961a | [log] [tgz] |
|---|---|---|
| author | iannucci <iannucci@chromium.org> | Sat Apr 29 03:07:26 2017 |
| committer | Commit bot <commit-bot@chromium.org> | Sat Apr 29 03:07:26 2017 |
| tree | dc9954c69bb4fc955746ada8b1ef81720e5c6308 | |
| parent | d84fead2a2eb7e0fe72c928fca0086df619509d9 [diff] |
[third_party] vendor argparse. Unfortunately some of the machines we run recipes on are woefully out of date, and there's a bugfix from 2014 in argparse that we need for consistent behavior across platforms. The delta for this argparse v. the old one is very small. You can see the diff here: https://github.com/python/cpython/commit/af26c15110 R=dnj@chromium.org, phajdan.jr@chromium.org BUG= Review-Url: https://codereview.chromium.org/2848493002
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!
bootstrap/
Bootstrapping and vendoring related code.
doc/
Documentation for the recipe engine (including this file!). Also includes doc/recipes.py, which is a file you can include in your repository to start using recipes. 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.
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 their example.py files.
recipe_engine/
The core functionality of the recipe engine. Noteworthy files include:
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\nR=joe@example.com" # This will ask for your Google Account credentials. git cl upload -s # Wait for LGTM over email. # Check the commit queue box in codereview website. # Wait for the change to be tested and landed automatically.
Use git cl help and git cl help <cmd> for more details.