commit | 6847560c6fadb39498faba723015698e9d3740c4 | [log] [tgz] |
---|---|---|
author | Struan Shrimpton <sshrimp@google.com> | Tue May 21 16:21:11 2024 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 21 16:21:11 2024 |
tree | a13a32c778731ab552605c5b3db5b74ac03232cc | |
parent | 8d37f2ed945da95325d8b256aa261d34e2c9100f [diff] |
utr: add an unwrap function to resultdb The utr is going to support rerunning from a swarming task which means we need to be able to unwrap the command to get the original raw cmd. Adding the unwrapping in recipes-py to keep the assumptions in one place. Bug: 41492686 Change-Id: Iaf41bb6d50d4465e9bd040e622299146a4a63073 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/5551967 Reviewed-by: Patrick Meiring <meiring@google.com> Commit-Queue: Struan Shrimpton <sshrimp@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.