commit | d8993f4684839b58f5f966dd6273d1d8fd001eae | [log] [tgz] |
---|---|---|
author | Weiwei Lin <weiweilin@google.com> | Wed Apr 21 04:10:10 2021 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 21 04:10:10 2021 |
tree | 633d733494e563e4be0ffd7a557749ba95320dba | |
parent | 91d88f5f33de9779cc396cfe0e8d17edb078a8ab [diff] |
[recipe] Update test presentation config to match lucicfg implementation 1. Renamed the property to '$recipe_engine/resultdb/test_presentation'. 2. Moved config_test_presentation from MiloAPI to ResultDBAPI. R=nodir, vadimsh Bug: 1191820 Change-Id: Ie589bf685a03268e107ab065030a805b0c8c1d04 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2838525 Commit-Queue: Weiwei Lin <weiweilin@google.com> Reviewed-by: Nodir Turakulov <nodir@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.