commit | ece005ce6b602d8ce89184853a11dfe1955b3ffd | [log] [tgz] |
---|---|---|
author | Garrett Beaty <gbeaty@chromium.org> | Thu May 23 18:40:43 2024 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 23 18:40:43 2024 |
tree | a44221939a383860b565e55c48f60ff1f0c4d21b | |
parent | c7dbdce8078cccf25330be5f86bf6e2370d37d44 [diff] |
Support Paths as arguments to Path.joinpath. This more closely aligns with the pathlib Path type, which enables pathlib Paths and strings to be used as arguments, with absolute or relative paths being handled for both types. The recipe Path type is always absolute, so anything occurring before a Path argument can be ignored. Bug: 329113288 Change-Id: I19894e9c1274d43ba8f370e9666c2add2a8c05c9 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/5558376 Commit-Queue: Garrett Beaty <gbeaty@google.com> Auto-Submit: Garrett Beaty <gbeaty@google.com> Reviewed-by: Robbie Iannucci <iannucci@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.