Google Git
Sign in
chromium / infra / luci / recipes-py.git / 28810c312f53fe68c22c9dcc8c6ef11f98590bd7
commit28810c312f53fe68c22c9dcc8c6ef11f98590bd7[log] [tgz]
authorChan Li <chanli@chromium.org>Tue Sep 14 20:42:13 2021
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Sep 14 20:42:13 2021
tree84da403a5bc1577ac66c5d72b8fcdcb9c12498e3
parent4a8ab7ed0d95dfd0b8886513fa6848ebe534b53d [diff]
[recipe-py] expose resultdb info in LUCI_CONTEXT

So that resultdb recipe module could get the current invocation from LUCI_CONTEXT instead of buildbucket, then we could remove resultdb->bb dependency.

Bug: 1245438
Change-Id: I839cc3452dce656ef20359c06091f4e030326f23
Recipe-Manual-Change: build
Recipe-Manual-Change: build_limited
Recipe-Manual-Change: chrome_release
Recipe-Nontrivial-Roll: depot_tools
Recipe-Manual-Change: fuchsia
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3153276
Commit-Queue: Chan Li <chanli@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
11 files changed
tree: 84da403a5bc1577ac66c5d72b8fcdcb9c12498e3
  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.