commit | 7c53ea7f7671c0e33dc0a95a2f87abbcb76c95fc | [log] [tgz] |
---|---|---|
author | Oliver Newman <olivernewman@google.com> | Wed Mar 10 03:21:09 2021 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 10 03:21:09 2021 |
tree | 1737d0a974cd584c3ea87faa6a76323a3ca9edab | |
parent | 921d2cffbab87ffa5cf8f86cc48e01954b251d46 [diff] |
[cipd] Accept ensure files as paths There are some CIPD use cases that involve checking an ensure file into git as a means of pinning a version of a tool. We'd like to be able to install tools based on these ensure files within a recipe, so make it possible to call `ensure()` on a pre-existing ensure file at a specified path in addition to a dynamically constructed ensure file. Change-Id: I27fe552bcd5460a1b71b96cb4083214099ca3162 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2747674 Commit-Queue: Oliver Newman <olivernewman@google.com> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Auto-Submit: Oliver Newman <olivernewman@google.com> Reviewed-by: Vadim Shtayura <vadimsh@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.