commit | c86ec65de1f1963306aa89b08b88ad0b011a39f4 | [log] [tgz] |
---|---|---|
author | Quinten Yearsley <qyearsley@chromium.org> | Thu Nov 05 22:01:00 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Nov 05 22:01:00 2020 |
tree | b1e466b3b3262876f3df074272900e95b429f5ad | |
parent | 3bbea7ca3f4d098731f5b507e2d8c7a6d791823b [diff] |
tricium: Expand the tricium recipe module to support wrapper recipes Wrapper recipes need to fetch analyzer CIPD packages, prepare input data, run the recipes, and accumulate results. This change adds support for such recipes. Bug: 1105239 Change-Id: I0cf7786db35e0a956739ee6d3bb45def3fe84424 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2513481 Commit-Queue: Quinten Yearsley <qyearsley@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Marc-Antoine Ruel <maruel@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.