| commit | 15b7962d99c005a8be0a89ddb1b84e7702ac7636 | [log] [tgz] |
|---|---|---|
| author | Robert Iannucci <iannucci@chromium.org> | Fri May 24 17:19:12 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Fri May 24 17:19:12 2019 |
| tree | f7f2ba6f1be727c70d94e85e506fb7e79e8397aa | |
| parent | f0bc0f54100ab943dda962c8922239922f48773a [diff] |
Reland Add gevent to recipe engine. This doesn't expose gevent to recipe userspace yet, but it changes the way that we run steps. IO processing is now done with gevent and subprocess42 is dropped. Includes a workaround for leaking processes/handles on windows for steps which daemonize. Due to a trifecta of ancient bugs which are all fixed in python3, we'll end up continuing to leak handles (but no more than we already leaked with subprocess42). R=tandrii@chromium.org Bug: 910369 Change-Id: Ib542c918f5f5c5d7f34874e07369c67c97cdcb83 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1626875 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.