| commit | a9965e67ca60668881a4ebe7afa62a581684149e | [log] [tgz] |
|---|---|---|
| author | Akash Mukherjee <akashmukherjee@google.com> | Mon Oct 10 17:10:19 2022 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Oct 10 17:10:19 2022 |
| tree | 12295931f1c705cef82e5b9fca91891fa38b2976 | |
| parent | 15dba9dcd3a474b6cdc00bd5529888dc8e78432b [diff] |
[bcid] Update the recipe step name to reflect usage. The steps here for bcid reporter has been ambiguous causing problem for oncallers to know the source of failure, happened earlier today in cros. Making it clear here what is the issue where a recipe fails is going to be very useful. R=jclinton@chromium.org CC=engeg@google.com Bug:b/245446268 Change-Id: I769492378185d79f395db7498cc8618a725117ca Recipe-Nontrivial-Roll: build_limited Recipe-Nontrivial-Roll: infra Recipe-Nontrivial-Roll: chrome_release Recipe-Manual-Change: chromiumos Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3938392 Reviewed-by: George Engelbrecht <engeg@google.com> Reviewed-by: Jason Clinton <jclinton@chromium.org> Commit-Queue: Akash Mukherjee <akashmukherjee@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.