commit | 1ddf2b83ae3565d58d8efab23249a6277a0fac85 | [log] [tgz] |
---|---|---|
author | Scott Lee <ddoman@chromium.org> | Tue Sep 29 17:24:09 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 29 17:24:09 2020 |
tree | d575ff1f0dae3ac54c2d4c985d1e1b4235892279 | |
parent | 69e35c3f12132996e3699c66cc802f482dc3adfb [diff] |
[resultdb] add param 'base_tags' to api.resultdb.wrap -tag was added by https://crrev.com/c/2435049. R=chanli@chromium.org,iannucci@chromium.org CC=nodir@chromium.org Change-Id: Ie099deae2896baeca7a1eaab622d859a95bb93c6 Bug: 1099573 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2436999 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Scott Lee <ddoman@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.