| commit | 6473859b070ab4e25c0c134ff3f5efd14134c5e7 | [log] [tgz] |
|---|---|---|
| author | Mateusz Zbikowski <zbikowski@google.com> | Mon Feb 06 18:52:08 2023 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Feb 06 18:52:08 2023 |
| tree | b4c1b4ebf49d7a2c2e0a83d215902ceb7e34e0a4 | |
| parent | 030e1286cc84be214129a6b48dd5f870d62d0090 [diff] |
Skip placeholder for get_file in url recipe module It's not made available to the caller anyway. This will allow for large downloads in 3pp. Path is only passed into _get_step by the get_file variant, so we can use bool(path) to determine if placeholder should be used. Bug: 1371140 Change-Id: I0ed26cbffa40a8a60e631801d835df48db592b7f Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/4218112 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Mateusz Zbikowski <zbikowski@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.