| commit | 52a5a6213721dd87f3b7213c4e2d5d32aa7daa3a | [log] [tgz] |
|---|---|---|
| author | Robert Iannucci <iannucci@chromium.org> | Tue May 02 17:11:17 2023 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 02 17:11:17 2023 |
| tree | c99101f12b6f5dc774e82e298c62f7f77c2f4b86 | |
| parent | 1b4211f38c7a4be6ce7cf7a7da90323c528e0833 [diff] |
Set py3_only for recipe-engine. Because of the way the integration tests work, this also required updating basically all the tests. I converted all tests in the engine repo to pass under python3, adjusting their shebang lines, etc. Running them under python2 will likely no longer work, but python2 is not fully ripped out in this CL. `git cl presubmit` now runs cleanly for me w/ vpython3 in PATH. Fixes a cadre of bugs which were related to running the tests and/or python2, and/or python3 conversion things which were missed. R=yiwzhang@google.com Bug: 1298328 Change-Id: Ida8f038aa63ff07e6d7b1f8d80f8ec63dd269c4d Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/4350877 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: 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.