commit | 33fed4343ba9723f8d4e16dd04978f27490f0a57 | [log] [tgz] |
---|---|---|
author | Garrett Beaty <gbeaty@chromium.org> | Thu Feb 13 20:04:06 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Feb 13 20:04:06 2020 |
tree | edf2fdc7280d9e98414a899614d5fd1dc20d152d | |
parent | ee858e5e410b4d30b666b29ebd759866300a5504 [diff] |
Report run steps in the order they were run. For a test failure, the steps that were run are reported to the user, but they are in an arbitrary order. Instead, order them according to the order the steps were run so that the used can more easily find where an error has occurred. Change-Id: I5b38e61401a7cd93d9ec47db5abf8944ee0235ae Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2055364 Auto-Submit: Garrett Beaty <gbeaty@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@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.