commit | b2839ad3882c5f1412afbd31f72c45355e404932 | [log] [tgz] |
---|---|---|
author | Oliver Newman <olivernewman@google.com> | Tue May 26 21:55:50 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 26 21:55:50 2020 |
tree | 242676b724ad00cbe72d0db4c8c6dac83f10d9e0 | |
parent | 923fb4bfa6f6930bac2ba3f03162ce8c59e0eb93 [diff] |
[cipd] URL-encode version in tool path Windows doesn't allow colons in paths, but quite a few CIPD package versions have colons in them, like "git_revision:abc". To avoid breaking builds on Windows we can url-encode the version before appending it to the path. Recipe-Nontrivial-Roll: fuchsia Change-Id: Ib980e18413ca4bc1cd29669bfb9e5af2f4ad20c7 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2216691 Commit-Queue: Oliver Newman <olivernewman@google.com> 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.