commit | 4cb1bf0fb0cb3c59f56399aa92a6c7956ef20e41 | [log] [tgz] |
---|---|---|
author | Garrett Beaty <gbeaty@chromium.org> | Mon May 02 16:53:58 2022 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 02 16:53:58 2022 |
tree | a886f6db5e79113eb9edc3122998844fdd49d460 | |
parent | f2754bcd62e3ac64580dedbe306b5ef519e44614 [diff] |
Don't set the -u flag when running python unbuffered. The PYTHONUNBUFFERED environment variable is set to 1 in the environment, so setting the -u is unnecessary. Removing it will minimize diffs when removing uses of the python module in a behavior-preserving manner. Bug: 1271425 Change-Id: I5f66bc0b1b25580ee8a3d8beedfd54dd6e8c9f4b Recipe-Nontrivial-Roll: build Recipe-Nontrivial-Roll: build_limited Recipe-Nontrivial-Roll: chrome_release Recipe-Nontrivial-Roll: chromiumos Recipe-Nontrivial-Roll: depot_tools Recipe-Manual-Change: infra Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3614862 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Garrett Beaty <gbeaty@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.