| commit | d459837f12b4d8d7e032c9b474d9a23f6935ff35 | [log] [tgz] |
|---|---|---|
| author | Alexander Thomas <athom@google.com> | Mon Jan 06 13:46:14 2020 |
| committer | Commit Bot <commit-bot@chromium.org> | Mon Jan 06 13:46:14 2020 |
| tree | 81172a3c0e14320fe3f2ac2c24d79accfc1b4e17 | |
| parent | 5591fe66be52b94aab70120f5401343521aaa4cc [diff] |
[swarming] Add bot_id property to TaskResult Bug: 1035790 Change-Id: Ib7f0d52f21fca8b3f1c400d8e1500f866b39e47d Recipe-Nontrivial-Roll: build Recipe-Nontrivial-Roll: build_limited_scripts_slave Recipe-Nontrivial-Roll: chromiumos Recipe-Nontrivial-Roll: fuchsia Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1975750 Commit-Queue: Alexander Thomas <athom@google.com> Reviewed-by: Junji Watanabe <jwata@google.com> Reviewed-by: Joshua Seaton <joshuaseaton@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.