commit | 86003d0c34d194b08701a0cca237b5d33fff4a26 | [log] [tgz] |
---|---|---|
author | Robert Iannucci <iannucci@chromium.org> | Mon May 20 23:50:39 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Mon May 20 23:50:39 2019 |
tree | 86b11623d2298face72110adcde4bc5440cb5a80 | |
parent | 4579203e4d12ba6ea65ecaf040ac4cf2e4e5f632 [diff] |
Add "pipe" helpers for multiprocess communication. These will be used in the new test runner implementation. R=tandrii@chromium.org Bug: 910369 Recipe-Nontrivial-Roll: skia Change-Id: I3a38d18c84d126f7d4b517bb613cac91c3f776c0 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1619034 Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Auto-Submit: 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.