Google GitGoogle Git
Sign in
chromium/infra/luci/recipes-py/29fbdcc7b7e5f04e34494717dd72d0e1cd2f8496
commit
29fbdcc7b7e5f04e34494717dd72d0e1cd2f8496
[log]
author
Robbie Iannucci <iannucci@google.com>
Fri Sep 04 16:28:18 2026
committer
LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>
Fri Sep 04 16:28:18 2026
tree
8ca8092742b47d37b8b4a24a759fdf3efebc13d8
parent
5e624bcadb9c666a98903b187b9bbb052a45703b [diff]
Revert "VPython: convert legacy vpython to UV for recipes-py."

This reverts commit 5e624bcadb9c666a98903b187b9bbb052a45703b.

Reason for revert: Downstream rollers are stuck/broken

Failure Link: https://ci.chromium.org/ui/p/infra/builders/try/Build%20Recipes%20Tester/b8671575233226713569/overview

Original change's description:
> 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>

Bug: b/491263752
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Change-Id: I92dd7a27f4b9b2c5795051325d5f9ed3ecadbfd9
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/8356711
Auto-Submit: Robbie Iannucci <iannucci@google.com>
Commit-Queue: Robbie Iannucci <iannucci@google.com>
Commit-Queue: rubber-stamper@appspot.gserviceaccount.com <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: rubber-stamper@appspot.gserviceaccount.com <rubber-stamper@appspot.gserviceaccount.com>
18 files changed
tree: 8ca8092742b47d37b8b4a24a759fdf3efebc13d8
  1. doc/
  2. infra/
  3. misc/
  4. recipe_engine/
  5. recipe_modules/
  6. recipe_proto/
  7. recipes/
  8. turboci/
  9. unittests/
  10. .editorconfig
  11. .gitattributes
  12. .gitignore
  13. .pycharm.vpython3
  14. .style.yapf
  15. .vpython3
  16. .vscode.vpython3
  17. AUTHORS
  18. codereview.settings
  19. CONTRIBUTORS
  20. GEMINI.md
  21. LICENSE
  22. OWNERS
  23. PRESUBMIT.py
  24. pyproject.toml
  25. README.md
  26. README.recipes.md
  27. recipe.warnings
  28. recipes.py
  29. SECURITY_TEAM_OWNERS
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.