commit | 34f49e8290e45a4c3c0ddd1e607e77dfac5d0f30 | [log] [tgz] |
---|---|---|
author | Robert Iannucci <iannucci@chromium.org> | Tue Jun 16 21:54:47 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 16 21:54:47 2020 |
tree | a58f61c59878e5c1ebda570d1ef01989f4051ace | |
parent | 156812241c03473af810c215981e482fb44ca42a [diff] |
[led] Update led module to use JSONPB for intermediate result format. Also overhuals the mocking system. Most recipes will not need to provide any led mocks in their recipe tests. R=tandrii@chromium.org, yiwzhang@chromium.org Bug: 1071627 Recipe-Manual-Change: build Recipe-Manual-Change: chromiumos Recipe-Manual-Change: fuchsia Change-Id: I0e438c0f263f9823494e82ce33fc287e49cf2007 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2188920 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.