| commit | 1cc8317a701750c47ac3fe5183af8e105f9c36bc | [log] [tgz] |
|---|---|---|
| author | Andrii Shyshkalov <tandrii@google.com> | Tue Oct 08 20:54:41 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Tue Oct 08 20:54:41 2019 |
| tree | 21ea10754a76e7cee591c47e94b22f373725a516 | |
| parent | 3d26d5f05680aa707e527b8c291d298cd3d35748 [diff] |
swarming: always mock bot and task IDs in test mode. Recipes are now always executed on top of swarming, but not every test fakes swarming environment nor should it. This will indicate realistic impact of CLs relying on swarming task id being present like https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1846932 R=vadimsh Change-Id: I6cd7f1052617899f4926a7066601d46b1a15a962 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1846717 Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Auto-Submit: 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.