commit | f6fc910b1f87c6d0d8757b9d40557a1caf75d506 | [log] [tgz] |
---|---|---|
author | Robert Iannucci <iannucci@chromium.org> | Fri Sep 11 16:55:27 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 11 16:55:27 2020 |
tree | c3fbf07e6fa202d6d76be3520a11df6db83e4530 | |
parent | 02cdffb4e155ba27e2c90142998faaeb1d788b0a [diff] |
[recipes.py] Use exec on *nix and ignore signals on Windows. This doesn't directly affect the signal handling characteristic of recipes in production (since they don't use this wrapper), but it helps for local debugging. On windows I've verified that ignoring signals in this wrapper program still sees them in the child program. R=yiwzhang@google.com Bug: 1127089 Change-Id: Iddac756d443a736030e36897b468deb5e3e5dd99 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2404570 Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Auto-Submit: 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.