commit | 29f83f0b60ed4debf5349aaa91019200a7a19357 | [log] [tgz] |
---|---|---|
author | Andrii Shyshkalov <tandrii@chromium.org> | Wed May 29 00:03:39 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Wed May 29 00:03:39 2019 |
tree | 958c18acacc5982bf8c506223a67b225f439b931 | |
parent | 295d478e0b3dc060e50fdba37edbf6552cc8796c [diff] |
cq: add .experimental and .top_level properties. These are set in by CQ service and passed via $recipe_engine/cq property. Follow up CL will propagate .experimental property as is and .top_level=False when triggering child builds via api.buildbucket. R=iannucci Bug: 964459 Change-Id: I7a9d360c6a507203acd813eeccc0bceeb4b05566 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1623921 Commit-Queue: Andrii Shyshkalov <tandrii@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.