commit | 6fca1db109d6dcc1083a751c7fafa8095db0a009 | [log] [tgz] |
---|---|---|
author | Garrett Beaty <gbeaty@chromium.org> | Wed Sep 04 23:04:51 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Sep 04 23:04:51 2019 |
tree | 24d4df739ea01d2890234061a22500e13b7de763 | |
parent | a3870eec10769a883eebbc3a0a08592742e56f5b [diff] |
Enable specifying test data in RecipeTestApi.test. Combining TestData objects using + produces awkward formatting when using yapf because when formatting arithmetic expressions it will squeeze multiple operands onto a single line when they fit. This can hide some of the test data when scanning code. yapf handles arguments to a function well, so accepting test_data as part of RecipeTestApi.test will produce readable, regular formatting. Bug: 998166 Change-Id: I2f877b5a0108ef6d90f4bc65ed6984485bb1c8f8 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1773426 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Garrett Beaty <gbeaty@chromium.org>
Recipes are a domain-specific language (embedded in python) for specifying sequences of subprocess calls in a cross-platform and testable way.
They allow writing build flows which integrate with the rest of LUCI.
Documentation for the recipe engine (including this file!). Take a look at the user guide for some hints on how to get started. See the implementation details doc for more detailed implementation information about the recipe engine.
user.email
and user.name
are configured in git config
.Run the following to setup the code review tool and create your first review:
# Get `depot_tools` in $PATH if you don't have it git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git $HOME/src/depot_tools export PATH="$PATH:$HOME/src/depot_tools" # Check out the recipe engine repo git clone https://chromium.googlesource.com/infra/luci/recipes-py $HOME/src/recipes-py # make your change cd $HOME/src/recipes-py git new-branch cool_feature # 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.