| commit | dca9d71d5c304f7817161d262f30f36fabd3699a | [log] [tgz] |
|---|---|---|
| author | Yiwei Zhang <yiwzhang@google.com> | Sat Jul 10 01:23:42 2021 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Jul 10 01:23:42 2021 |
| tree | 7f42413adf927bb7d6d783443fc926012d21f47a | |
| parent | fc00fd8eb7a87ee6ed8cf80f02b762e28f02fe36 [diff] |
py3: read stdin in binary mode as a regular file sys.stdin.read() in python 3 will return text instead of bytes-like object which is not what protobuf decoder expects. Technically, we can switch to use sys.stdin.buffer.read() here but that would mean branching code in order to support both py2 and py3. R=iannucci, yuanjunh Bug: 1227763 Change-Id: I27d68730b7f2e708cea199aacfebd75cdff84f01 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3018053 Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Auto-Submit: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Yuanjun Huang <yuanjunh@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.