| commit | 9e184408eba22447467cbb4f506cfeef745a8182 | [log] [tgz] |
|---|---|---|
| author | Robert Iannucci <iannucci@chromium.org> | Fri Dec 03 21:58:59 2021 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 03 21:58:59 2021 |
| tree | a737fbd8726ffd4f7c22482a5389effff0a22633 | |
| parent | 6fc52ceac19cb00ced1b7976056c9e61add3868f [diff] |
Make python warning system work for warnings issued within greenlets. For example, if you do `api.futures.spawn(api.python.inline, ...)`, and `api.python.inline` issues a warning, the stack evaluation system will get confused because it can't look past the top of the greenlet stack. This will allow it to continue the stack evaluation from where the greenlet was created. Additionally, this refines the 'recipe code' stack filter to only consider recipe and module code to be 'recipe code' (which allows it to work properly in the recipe_engine repo, which picks up stuff in the recipe_engine folder) R=yiwzhang, yuanjunh Change-Id: I5295873c666ad00a9bb4cc2368c044928e76c8e3 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3314497 Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@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.