commit | 283e15116d842a492c911212db27c33cdf6858ab | [log] [tgz] |
---|---|---|
author | Rob Mohr <[email protected]> | Mon May 05 19:32:25 2025 |
committer | LUCI CQ <[email protected]> | Mon May 05 19:32:25 2025 |
tree | a32d30a6d430985d66dd822b6ccdf3fad6c0ab25 | |
parent | 65c813d875090daf9ec663842adbde864724c642 [diff] |
[buildbucket] Add RPC explorer link to search() Add a link to the buildbucket RPC explorer that makes it trivial to reproduce the query. Change-Id: I1a56621c489e8df7a93ae470e98c89e1e4dfe266 Recipe-Nontrivial-Roll: build Recipe-Nontrivial-Roll: build_internal Recipe-Nontrivial-Roll: chromiumos Recipe-Nontrivial-Roll: fuchsia Recipe-Nontrivial-Roll: pigweed Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/6511326 Reviewed-by: Chan Li <[email protected]> Commit-Queue: Rob Mohr <[email protected]>
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 [email protected] # 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.