| commit | 6126bc2f1092567bb3b0d96f0381330ba01ead75 | [log] [tgz] |
|---|---|---|
| author | Robert Iannucci <iannucci@chromium.org> | Thu Oct 01 22:12:15 2020 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Oct 01 22:12:15 2020 |
| tree | 5e7bf3193955c9d82d87bc7ff7c657b8aac6aab8 | |
| parent | d1f33ea19da098a03f6d019202bf967992b71ee1 [diff] |
[luci_context] Move writing of LUCI_CONTEXT files to the engine core. This removes an odd file-write from 'userspace' recipe code, but also enables compuation of 'timeout' for the step much closer to the actual step execution. Specifically, this avoids having 'timeout' also cover the time that we block for resource contention when running multiple greenlets in the recipe. R=vadimsh, yiwzhang Bug: 1127089 Change-Id: Iff59e7698e9556737a6144508c00cb3342811641 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2441885 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: 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.