commit | ad6afcb57861e86a926cdc22162e182b112c3d2c | [log] [tgz] |
---|---|---|
author | Robert Iannucci <iannucci@chromium.org> | Mon Sep 28 16:44:17 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Sep 28 16:44:17 2020 |
tree | 38698acc75c78fdc5c88e9d9599e25503491c64f | |
parent | 12ab0ef8c9da852fe9d026704f6042545b63a15b [diff] |
[runtime] Re-add is_luci PROPERTY to unblock roller. Legacy properties are VERY grumpy when they're supplied with a field that they have no definition for. Will convert this to the more sane proto-based PROPERTIES in a subsequent CL. Landing this first to allow the autoroller to resume without borking stuff. R=tikuta, yiwzhang, lamontjones Change-Id: I1fb20c4cb963bf1232a5402cadd730d3b21f38e2 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2434772 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: LaMont Jones <lamontjones@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: 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.