commit | c02bbc83a32cb6edb9de4a0a108ed1934075bc88 | [log] [tgz] |
---|---|---|
author | LaMont Jones <lamontjones@chromium.org> | Fri Sep 18 21:08:15 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 18 21:08:15 2020 |
tree | 58dfb76c044c17c3a4dd8bd741255548db1d6086 | |
parent | 7c33aeefa596b8af9fd017e591e3e5a4db47abb4 [diff] |
recipes.py: Run yapf Some autorolled recipes require yapf compliance in presubmit checks. Make recipes.py conform to allow autorolls to happen seamlessly. BUG=None Change-Id: Id359bf8dd7e8b4b3335d31ec09b2823e0be5a14a Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2417401 Auto-Submit: LaMont Jones <lamontjones@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: 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.