commit | 46311e5fca95329b511a45b42648ead457b2eea5 | [log] [tgz] |
---|---|---|
author | Garrett Beaty <gbeaty@chromium.org> | Tue May 21 23:29:51 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Tue May 21 23:29:51 2019 |
tree | 9e3808c577cf26e6407285c07f3a67fbe696ffef | |
parent | f0e05ce44e073ad5282ce65e200f29eab9d87666 [diff] |
Don't write annotations when running simulation tests. Instead of a stream engine that writes annotations, simulation tests will use a stream engine that collects the information directly in the form to be consumed by magic_check_fn.post_process and convert the results to the annotation format currently used in expectation files. This saves round tripping the dictionary between annotations and the values consumed by post-process hooks for each post-process hook. Change-Id: Ie979d145b915c7944bd4b81ca2853f1103c511ec Recipe-Nontrivial-Roll: chromiumos Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1579367 Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@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.