commit | 2307f31506c879bb57ddfed06c14ec3835bd27ff | [log] [tgz] |
---|---|---|
author | Robert Iannucci <iannucci@chromium.org> | Mon Sep 28 17:51:27 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Sep 28 17:51:27 2020 |
tree | cd360cf167b735b66f0ad4008b806e7bf1258f5e | |
parent | ad6afcb57861e86a926cdc22162e182b112c3d2c [diff] |
[runtime] Convert to proto based PROPERTIES, remove is_luci. Proto based properties are lenient to extra fields (they're ignored). Should prevent breakage such as the one we saw in the autoroller. R=lamontjones, tikuta, yiwzhang Change-Id: I7e9dde961ebadd122ee1aa07b2c810410959d91f Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2434773 Reviewed-by: LaMont Jones <lamontjones@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Auto-Submit: 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.