commit | a3a73586fd370ae8552482a6a6885c494c8c4b28 | [log] [tgz] |
---|---|---|
author | Yiwei Zhang <yiwzhang@google.com> | Wed Jul 21 23:27:47 2021 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 21 23:27:47 2021 |
tree | a882e52411cf623d0fec6d3ba7c21727728decc2 | |
parent | c80e36cb1fecf569f5b9e6da86722a90adf37ebe [diff] |
py3: upgrade parameterized to 0.8.1 and use new naming feature The test class will become LuciexeSmokeTest_PY2 and LuciexeSmokeTest_PY3 instead of LuciexeSmokeTest_0 and LuciexeSmokeTest_1 R=iannucci, yuanjunh Bug: 1227763 Change-Id: Ib194763f731e967e4468cccd82d8155d2f408a33 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3044627 Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Auto-Submit: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Robbie Iannucci <iannucci@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.