commit | 406f6a4a77f5c081bccd4718f8e10caddf9dc802 | [log] [tgz] |
---|---|---|
author | Robert Iannucci <iannucci@chromium.org> | Wed Sep 30 18:19:17 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 30 18:19:17 2020 |
tree | 9503dd732db6c2aa2febaf57b941197c9d701d05 | |
parent | e47e1156a8e28a697e3ac311164fc0071b43c72f [diff] |
Remove LUCI_CONTEXT from test simulations. As the comment says, the entire contents of the LUCI_CONTEXT are visible in the test expectations, so there's no need to put the fake temporary file variable in there, too. R=vadimsh, yiwzhang Bug: 1127089 Change-Id: Ie676e23bbf1d005bbda2b31da84b520e2775c894 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2439339 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: 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.