| commit | 8f6285ba602d2366d805eccac3471f2dd7ba0f68 | [log] [tgz] |
|---|---|---|
| author | Ye Kuang <yekuang@google.com> | Mon Sep 07 07:43:18 2020 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Sep 07 07:43:18 2020 |
| tree | 4b7f1835612696c49d1f8b0425631352d433e971 | |
| parent | 4efc10de7c33a61e6c806100ecea187be2f9dccb [diff] |
Support verbose flag in swarming recipe module's trigger() API This is to align with https://source.chromium.org/chromium/chromium/tools/build/+/master:recipes/recipe_modules/chromium_swarming/api.py;l=880-881;drc=2081593d2703ad6e19bdfdbcef518cc1d3b11128 Bug: 894045 Change-Id: Ibd384c8075c00ac4e76cf504f8d59676f9da9895 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2395014 Commit-Queue: Ye Kuang <yekuang@google.com> Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Auto-Submit: Ye Kuang <yekuang@google.com> Reviewed-by: Takuto Ikuta <tikuta@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.