| commit | edb73a793557dcbdfe6854f27d90d3d488fa04ec | [log] [tgz] |
|---|---|---|
| author | Robert Iannucci <iannucci@chromium.org> | Wed May 29 19:32:35 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed May 29 19:32:35 2019 |
| tree | 9536e4202dbfbcffee75f76d7d452bb116e8b2e6 | |
| parent | 8b16a36e64065fb9a59237d9cbeb1b4123910e8f [diff] |
Make nested parent steps have strict scope. To sanely support concurrency, I need to make `api.step.nest` strictly scoped; i.e. once you leave the nest context it closes all the steps within that context. This completely removes the need to have any userspace-controlled step callbacks which the engine must run. This will significantly simplify the userspace exposure of gevent. I've already updated all the downstream repos to be trivially compatible with this change. Bug: 910369 Change-Id: Iad57edeb3dd6049702736ebe06461762b0d5fae4 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1629920 Commit-Queue: 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.