commit | b5549f35848315ca14765354aaa24200e992f640 | [log] [tgz] |
---|---|---|
author | Scott Lee <ddoman@chromium.org> | Wed Nov 13 01:14:35 2024 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Nov 13 01:14:35 2024 |
tree | d6c8f29097a2079834b8a4ae52c9653243377b3f | |
parent | 69f6932e1e1f36304e86227a317ce226ad5338c7 [diff] |
[recipe_proto] sync findings.proto with the latest copy to pick up the changes from https://crrev.com/c/6004562 Bug: 372748699 Change-Id: If3a564d81740af09ccc7f8b30a3a8f12a35b6f57 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/6013097 Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Auto-Submit: Scott Lee <ddoman@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@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.