cq: upgrade recipe_module to use protobuf message as input.

R=iannucci

Bug: 966979
Change-Id: I945a6ff5ef308e68615a3cf25554c26dcdacccb7
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1629735
Auto-Submit: Andrii Shyshkalov <tandrii@chromium.org>
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
9 files changed
tree: c7a18ac6e70186589b2e4cfc510978a7e66a6bf8
  1. .gitattributes
  2. .gitignore
  3. .style.yapf
  4. .vpython
  5. AUTHORS
  6. CONTRIBUTORS
  7. LICENSE
  8. OWNERS
  9. PRESUBMIT.py
  10. README.md
  11. README.recipes.md
  12. codereview.settings
  13. doc/
  14. infra/
  15. misc/
  16. recipe_engine/
  17. recipe_modules/
  18. recipe_proto/
  19. recipes.py
  20. recipes/
  21. unittests/
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.