commit | ba2e549fc2f9cc837deb0a69789067c74021e38e | [log] [tgz] |
---|---|---|
author | Alex Zamorzaev <zamorzaev@chromium.org> | Tue Jun 02 18:20:04 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 02 18:20:04 2020 |
tree | 04572b4f08c86361e53db35eb5bc51ae3f4cb27c | |
parent | 5c575266cf91a14adf9b17c71f4e4e03ad964c24 [diff] |
cipd: Fix set_ref, set_tag JSON parsing The current module implemtation fails to parse the JSON produced by the current cipd binary. Tested via led get-build 8878654566857571744 | led edit-recipe-bundle -O recipe_engine=/usr/local/google/home/zamorzaev/infra/recipes-py/ | led launch Bug: 1090226 Change-Id: Icf0a01e54ed94f38b6d16b0dcd7bf98637172b22 Recipe-Nontrivial-Roll: chromiumos Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2226126 Commit-Queue: Alex Zamorzaev <zamorzaev@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Vadim Shtayura <vadimsh@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.