Google Git
Sign in
chromium / infra / luci / recipes-py / 8e0e2eccd8311b1baf4a1a3da953e29884be3720
commit8e0e2eccd8311b1baf4a1a3da953e29884be3720[log] [tgz]
authorBenjamin Shai <bshai@google.com>Wed Mar 29 21:23:32 2023
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Mar 29 21:23:32 2023
tree4d556e57af26c3b4fa9cc7a15ef69abd1c2b3cd7
parent0cb83e45e5970dea6a3b3cd30eb7c70c904cd51c [diff]
runner: generalize status warnings

This commit adds the support for creating general warnings and
emitting them, and switches over the status check to use this more
generalized approach.

(Incidentally, this also fixes a bug with the status warnings where
they were always emitting "SUCCESS" as the test's status.)

Change-Id: I54fa4e7eddeeabf8c893d833373d62e0c8c920b3
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/4383112
Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
Auto-Submit: Benjamin Shai <bshai@google.com>
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
4 files changed
tree: 4d556e57af26c3b4fa9cc7a15ef69abd1c2b3cd7
  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. recipe.warnings
  24. 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.