commit | e052ab8a109530acf15ce7cea440ad9a3f6f2f38 | [log] [tgz] |
---|---|---|
author | Oliver Newman <olivernewman@google.com> | Tue Dec 01 18:31:53 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 01 18:31:53 2020 |
tree | 21d5085c9d9c39d34bffe3df83fdfa01e069d83f | |
parent | 576a243a4c291e0659adaead31e77043e6dcbf14 [diff] |
[json] Indent mock json data This makes JSON data in expectation files much more readable. It only applies to unit tests, and should have no effect on production recipe runs. Recipe-Nontrivial-Roll: build Recipe-Nontrivial-Roll: infra Recipe-Nontrivial-Roll: chrome_release Recipe-Nontrivial-Roll: chromiumos Recipe-Nontrivial-Roll: fuchsia Change-Id: Ib14a852d6e1c6b418fe0f946121380671ecae752 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2561468 Auto-Submit: Oliver Newman <olivernewman@google.com> Commit-Queue: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
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.