commit | 1b1ecd03e0b00399784c43add1465f685b6d1ab9 | [log] [tgz] |
---|---|---|
author | Oliver Newman <olivernewman@google.com> | Tue Feb 01 19:43:21 2022 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 01 19:43:21 2022 |
tree | 56d5ed0942457cb34d98b56642efc1b2e357e4f7 | |
parent | 5675f7012878c187ba4d9556be2944fc00744bbf [diff] |
[recipes.py] Set --quiet on git fetch I changed the `git fetch` call in crrev.com/c/3381274 to not swallow stderr with the intent of not hiding error messages, but now it's overly noisy. By setting --quiet it will only print errors, no informational output. Change-Id: I2656df939af4d1fa17a4d7ed4e2a9456f9c9187f Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3428077 Commit-Queue: Oliver Newman <olivernewman@google.com> Auto-Submit: Oliver Newman <olivernewman@google.com> Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: 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.