Google Git
Sign in
chromium / infra / luci / recipes-py / 25cfc72ac2ece1be4ebb314c8c71b87b75eda688
commit25cfc72ac2ece1be4ebb314c8c71b87b75eda688[log] [tgz]
authorRobert Iannucci <iannucci@chromium.org>Fri Mar 22 19:28:40 2024
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Mar 22 19:28:40 2024
treec84cfbdaa7e665394dea64b0cce5b174ed7584e3
parent495104ac9720d9b63e22b09f8270f3aaa5415225 [diff]
Rename UnresolvedRequirement.

This is a simple refactor to make a later CL smaller - This type
should have a public name because it's useful to put in type
annotations in other files.

R=bpastene, bryner, sshrimp

Bug: 329113288
Change-Id: I0c21104aceb3ba16d92b54686c8cffba74ccb5ab
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/5379172
Reviewed-by: Rob Mohr <mohrr@google.com>
Reviewed-by: Brian Ryner <bryner@google.com>
Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
Auto-Submit: Robbie Iannucci <iannucci@chromium.org>
7 files changed
tree: c84cfbdaa7e665394dea64b0cce5b174ed7584e3
  1. doc/
  2. infra/
  3. misc/
  4. recipe_engine/
  5. recipe_modules/
  6. recipe_proto/
  7. recipes/
  8. unittests/
  9. .gitattributes
  10. .gitignore
  11. .pycharm.vpython3
  12. .style.yapf
  13. .vpython3
  14. .vscode.vpython3
  15. AUTHORS
  16. codereview.settings
  17. CONTRIBUTORS
  18. LICENSE
  19. OWNERS
  20. PRESUBMIT.py
  21. pyproject.toml
  22. README.md
  23. README.recipes.md
  24. recipe.warnings
  25. 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.