| commit | 8fd8dc56140820b86ce0bda8c61a66021413c9d6 | [log] [tgz] |
|---|---|---|
| author | Oliver Newman <olivernewman@google.com> | Fri Sep 06 00:26:20 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Fri Sep 06 00:26:20 2019 |
| tree | 0283e563cd737a022b2a73dca5744ee8d9525ee3 | |
| parent | 852662ebd96dfb039d8f8300991000da4ba69b93 [diff] |
[led] Expose led run ID Led now sets a "led_run_id" recipe module property when it launches jobs: https://chromium-review.googlesource.com/c/infra/infra/+/1783704 Recipes can use this property instead of the "launched_by_led" property to determine if they are being executed as led jobs. We'll delete the launched_by_led property from led entirely once recipes no longer rely on it, since "led_run_id" conveys the same information. Bug: fuchsia:35999 Change-Id: Ib5d20273376842e305f2d3dcc76cdb2578644a14 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1788523 Reviewed-by: Joshua Seaton <joshuaseaton@google.com> Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Oliver Newman <olivernewman@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.