commit | 8305d8fd87b19e4f63db30ac7ea9d52f1fc2093c | [log] [tgz] |
---|---|---|
author | Robert Iannucci <iannucci@chromium.org> | Mon Jun 01 23:12:20 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 01 23:12:20 2020 |
tree | 8f6219ec3cef60d5dd5b278f2f52eaa1817f7d5e | |
parent | 5da0f45b944e9d5ea50d05d8c52a729a6a085ade [diff] |
[cipd] Make ensure_tool concurrency-safe. R=olivernewman@google.com, tandrii@chromium.org, vadimsh@chromium.org, yiwzhang@google.com Bug: 1015181 Recipe-Nontrivial-Roll: build Recipe-Nontrivial-Roll: chromiumos Recipe-Nontrivial-Roll: fuchsia Recipe-Nontrivial-Roll: build_limited_scripts_slave Recipe-Nontrivial-Roll: chrome_release Change-Id: I4980ab6e75919ca153f1a4a198a2033ca1c83366 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2223349 Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
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.