commit | 01b9c522df32a1f5d0dbb31e0b86bd22e3085bf1 | [log] [tgz] |
---|---|---|
author | Scott Lee <ddoman@chromium.org> | Thu Oct 08 15:28:31 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Oct 08 15:28:31 2020 |
tree | f15a8a7d27de16153250064fbba67b73dc31b4b4 | |
parent | 778c4c88bc5819d7527d9decd3d91919520ae32c [diff] |
[resultdb] add coerce_negative_duration to api.resultdb.wrap() The flag was added in https://crrev.com/c/2455175 to coerce nagative duration values to 0. Please find more context in crbug.com/1135892. R=chanli@chromium.org,nodir@chromium.org,martiniss@chromium.org Bug: 1135892 Change-Id: I14e6b8b35a8abb29466233a5d664be1e084152ba Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2458788 Reviewed-by: Chan Li <chanli@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Scott Lee <ddoman@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.