Google Git
Sign in
chromium / infra / luci / recipes-py / 4077ceeac827409f2a2953cd01aec6d29601decc
commit4077ceeac827409f2a2953cd01aec6d29601decc[log] [tgz]
authorQuinten Yearsley <qyearsley@chromium.org>Sat Dec 05 22:34:34 2020
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Dec 05 22:34:34 2020
tree6a08d568c822df91ce11b804172b3aaca55f13cd
parent424f90b51844a2c554b2e1ff3d444f72594f89c6 [diff]
Add a mapping of name to analyzer in tricium recipe module

In some tricium wrapper recipes, we may want to specify analyzers
via an input properties protobuf message. In this case, the easiest
way to specify analyzers is by listing names of predefined analyzers.

This CL adds a mapping to the tricium recipe to make it easier
to look up analyzers by name.

Bug: 1146109, 1155680
Change-Id: Ic2713b519b74fa8efeba30f1a5c4dc8a57a03a58
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2574733
Commit-Queue: Quinten Yearsley <qyearsley@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
2 files changed
tree: 6a08d568c822df91ce11b804172b3aaca55f13cd
  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. AUTHORS
  14. codereview.settings
  15. CONTRIBUTORS
  16. LICENSE
  17. OWNERS
  18. PRESUBMIT.py
  19. README.md
  20. README.recipes.md
  21. 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.