commit | c3529daae6c9b5e1a1ef8a02bbd7535e5917d09a | [log] [tgz] |
---|---|---|
author | Robert Iannucci <iannucci@chromium.org> | Thu Jul 11 20:11:38 2019 |
committer | Robbie Iannucci <iannucci@chromium.org> | Thu Jul 11 20:11:38 2019 |
tree | 3ec708fbb9fc442127023b11b32a45e3686c82fa | |
parent | 602257a66a4e492e7029ccaf542b55f9ef641346 [diff] |
[fetch] Actually fetch from the provided ref. Previously there was confusion around ref vs revision; The checkout function signature expected a ref, but was always being passed a revision. Now we pass both the ref and the revision when we have them; The fetch operation will now provide the ref during the fetch which should allow non-master refs. R=gbeaty@chromium.org, tandrii@chromium.org Change-Id: Ie14f7c3f388f90bfeb49ad8a4145c04305dee1b4 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1693768 Reviewed-by: Garrett Beaty <gbeaty@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> (cherry picked from commit b077e6d7b5e202070b28b0e7e1be95396c423eec) Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1698495
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.