commit | f4da958651245c502ddc163813f920c91adedd33 | [log] [tgz] |
---|---|---|
author | Garrett Beaty <gbeaty@chromium.org> | Wed Aug 23 21:09:56 2023 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Aug 23 21:09:56 2023 |
tree | 8a4a018c2c862ed5f1d0f6c6542f0c4f43e47c80 | |
parent | a8f6351f031cc57fa88ad23fba0631bd6a02b3e7 [diff] |
Add attempt_key property to cv recipe module. This will enable recipes to tag tasks and results with the cv attempt to simplify querying. Change-Id: Ia0b937ee71c164c73b9ccfce1cb738a1c61aa370 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/4791526 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Garrett Beaty <gbeaty@google.com> Auto-Submit: Garrett Beaty <gbeaty@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.