Google Git
Sign in
chromium / infra / luci / recipes-py / adf6ca4b1b34afab601637ef3fe9445b4cffb635
commitadf6ca4b1b34afab601637ef3fe9445b4cffb635[log] [tgz]
authorYuanjun Huang <yuanjunh@google.com>Thu Jul 29 23:15:03 2021
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jul 29 23:15:03 2021
tree421ae29de47c1c29baf0fefb83d5b2ce64a05b04
parent5f4efc864186ac5440ef77fc7282715b7355ce02 [diff]
[python3] make test _runner command py3 compatible

Make `test _runner` cmd be able to run in py3 env. After this CL,
users can specify `PYTHON_VERSION_COMPATIBILITY` in their recipes
and run both py2 and py3 simulation tests at the same time.

Note: don't set RECIPES_USE_PY3 sys env, as `test run/train` cmds
aren’t ready yet.

Bug:1211651
Change-Id: I6f7fe748a569fd8bc9949425eef8ed976e40e10b
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3057371
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
Commit-Queue: Yuanjun Huang <yuanjunh@google.com>
9 files changed
tree: 421ae29de47c1c29baf0fefb83d5b2ce64a05b04
  1. doc/
  2. infra/
  3. misc/
  4. recipe_engine/
  5. recipe_modules/
  6. recipe_proto/
  7. recipes/
  8. unittests/
  9. .gitattributes
  10. .gitignore
  11. .style.yapf
  12. .vpython
  13. .vpython3
  14. .vpython3_dev
  15. AUTHORS
  16. codereview.settings
  17. CONTRIBUTORS
  18. LICENSE
  19. OWNERS
  20. PRESUBMIT.py
  21. README.md
  22. README.recipes.md
  23. recipes.py
README.md

Recipes

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.

Contributing

  • Sign the Google CLA.
  • Make sure your 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.