VPython: convert legacy vpython to UV for recipes-py. The conversion is done with the `vpython3 -vpython-tool upgrade -legacy` command. In addition, legacy file references were amended, the now not working test checking match between the spec files, and added a test that confirm that the lock files content is up to date. Bug: b/491263752 Change-Id: I94bb5725a39cb722f2aea3f1af9223656a6a6964 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/8333268 Reviewed-by: Chenlin Fan <fancl@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@google.com> Commit-Queue: Alex Ovsienko <ovsienko@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.