commit | e051b6e61887a79ca02fa2f912163032754d7948 | [log] [tgz] |
---|---|---|
author | Robert Iannucci <iannucci@chromium.org> | Fri Oct 04 07:27:41 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Oct 04 07:27:41 2019 |
tree | b15227be9d0264eea52ea66d455ed9aa7bf147f8 | |
parent | cb5e29908c24ae791cbc0c1fc17e9098bc2157cc [diff] |
[context] Fix context module to use greenlet-specific storage. This adds a generic mechanism where ANY module can decide to use its own greenlet-specific storage (and get a callback whenever a spawn action happens). This also upgrades to Coverage 4.5.x, which fixes some bugs w.r.t. tracing concurrent code (and seems to also be a bit faster). R=tandrii@chromium.org Bug: 910369 Recipe-Nontrivial-Roll: fuchsia Change-Id: I47832dad26bc5f76d2f9ec4dc3f2772e5d020491 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1839615 Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
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.