commit | ee04e981697e98043a91855c4caf0e3ee0b99cd7 | [log] [tgz] |
---|---|---|
author | Struan Shrimpton <sshrimp@google.com> | Mon Aug 19 18:26:07 2024 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Aug 19 18:26:07 2024 |
tree | a28cc51a337da5fed1546fcd3df629121744c04b | |
parent | 39a4ee859137fd595ee5ad528f9347aaca46811c [diff] |
Add raise_on_failure option to update_invocation Now that instructions can be added to the invocation this call might not be critical if only the instructions are being updated. To avoid failing the build, allow a raise_on_failure parameter to get passed through to the step call. Bug: 349529661 Change-Id: Ic3d9e5b87331395d753bd417151c065e5fad8ee6 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/5793244 Commit-Queue: Struan Shrimpton <sshrimp@google.com> Reviewed-by: Tuan Nguyen <nqmtuan@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.