commit | 8c34b0b3f39e54354a7c6f0053ea0851e1a546a3 | [log] [tgz] |
---|---|---|
author | Rob Mohr <mohrr@google.com> | Mon Jan 08 21:24:19 2024 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jan 08 21:24:19 2024 |
tree | cc47ec49caabce287e1c5bed242f8d97a13a1d60 | |
parent | 1fb142e1c49362a52c88bbc40f5ccb12d810d5e7 [diff] |
[defer] Allow suppressing results in contexts Allow suppressing all previous results in a defer context, but only if there are additional failures. This is useful when we know a step has failed, but we can provide a better failure message for it by parsing the logs of the step in question. Change-Id: I1b25ba0f57bde41fe4c4db7ccb458e8d22658aa5 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/5171421 Reviewed-by: Yuanjun Huang <yuanjunh@google.com> Commit-Queue: Rob Mohr <mohrr@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.