commit | ffa22068932840841717bad394021f2eed164dfb | [log] [tgz] |
---|---|---|
author | Ina Huh <ihuh@google.com> | Thu Jun 20 04:29:41 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Jun 20 04:29:41 2019 |
tree | 258807b4ead029bc9d860ad995f0ea2f2703caf1 | |
parent | 3b29f4f04b7d504b5f9953d1d6d95f7b99363b08 [diff] |
[file] Fix json.dumps call in write_json to correctly take in indent parameter. Recipe-Nontrivial-Roll: chromiumos Recipe-Nontrivial-Roll: build Recipe-Nontrivial-Roll: infra Recipe-Nontrivial-Roll: skia Recipe-Nontrivial-Roll: build_limited_scripts_slave Recipe-Nontrivial-Roll: release_scripts Change-Id: Ia7a61ebd207c761e6d2d586fcfc8abcdb4ab74f7 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1668516 Reviewed-by: Joshua Seaton <joshuaseaton@google.com> Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Ina Huh <ihuh@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.