commit | 852fd411c26654207705fb9e0581942ce291f803 | [log] [tgz] |
---|---|---|
author | Scott Lee <ddoman@chromium.org> | Fri Mar 12 22:56:47 2021 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Mar 12 22:56:47 2021 |
tree | 417916cd01ffa5de323ed1822fbf9254ebb66292 | |
parent | 7c53ea7f7671c0e33dc0a95a2f87abbcb76c95fc [diff] |
with_resultdb() always set enable=True There is no reason to allow users to disable it by pasing a param to with_resultdb(). Users should have not invoked with_resultdb(), if ResultDB was not intended to be enabled. R=nodir@chromium.org,jwata@google.com you can land this upstream change. Once the upstream change lands, roll it into your downstream CL: Bug: 1099573 Change-Id: I7a85fdaa4a7a76d0a83771623da7023ed5034880 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2316459 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Junji Watanabe <jwata@google.com> 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.