| commit | 70eb7a77b1f8a2482dc1bf6dd09c337485c13ca8 | [log] [tgz] |
|---|---|---|
| author | Yiwei Zhang <yiwzhang@google.com> | Sat May 09 05:58:57 2020 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat May 09 05:58:57 2020 |
| tree | e691d1769b896199d1e1c77f7221b12efdc83a4a | |
| parent | c55f377bbc5b7d73ea7ac4d6504d6d6071a8fbf9 [diff] |
[luciexe] Always send one last build to lodgog before closing stream engine The build result is updated right before the stream engine is closed. Even though after the build result is updated we instruct a send, the actual send will not happen until gevent switch to the send greenlet thread. However, we might already close the stream engine before that so the build with result updated would never be sent to logdog. R=iannucci Change-Id: I3179d89b15baf6d9f8f752e4ae381cde094dae0f Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2191394 Auto-Submit: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@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.