| commit | 0afd693c9bf53a74e7c575891001a7e0d7491fae | [log] [tgz] |
|---|---|---|
| author | Garrett Beaty <gbeaty@chromium.org> | Tue Jun 15 00:24:42 2021 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 15 00:24:42 2021 |
| tree | 3dab94982b7260a7bde0684f984d7664f2551fe5 | |
| parent | 7dd172078b903b9a3639400d449d34478591deec [diff] |
Update StepCommandContains to support regexes. The cmd field of the steps provided to post_process functions already supports subsequence matching, including matching by regex. This implements StepCommandContains in terms of this functionality to reduce code duplication. The formatter handles code using StepCommandContains better than it does lambdas if the lines are long, so it still provides value. Change-Id: Ia056e74caab0d40e1900e77837bc4337a2dbcd9e Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2961169 Auto-Submit: Garrett Beaty <gbeaty@chromium.org> Commit-Queue: Stephen Martinis <martiniss@chromium.org> Reviewed-by: Stephen Martinis <martiniss@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.