| commit | f0e05ce44e073ad5282ce65e200f29eab9d87666 | [log] [tgz] |
|---|---|---|
| author | Robert Iannucci <iannucci@chromium.org> | Tue May 21 22:55:10 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Tue May 21 22:55:10 2019 |
| tree | 4381e79a083d9cd65abdea31c305e09f95f41a95 | |
| parent | 85fd521fdda1e253ba8b7f736bf2e69a446e2c8c [diff] |
Add functions for reporting new test result data to the user. These functions are not as 'clean' as they could be (i.e. printing directly to stdout), but it was more obscure to write them in a generalized fashion and the code doesn't benefit from such generalization currently (nor is expected to). Also emoji. R=tandrii@chromium.org Bug: 910369 Change-Id: I91c23663b856c8e48569ed7ad87656a142ce1b45 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1619426 Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
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.
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.