| commit | 12480dc56a771e1cae50ce7cdbf3f9df78e76043 | [log] [tgz] |
|---|---|---|
| author | Oliver Newman <olivernewman@google.com> | Wed Sep 22 15:27:59 2021 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 22 15:27:59 2021 |
| tree | 5ccee240de1bf990a660d279d7310b0410a563ee | |
| parent | f28ac0ab20025138a3f46845de09d625960c2a97 [diff] |
[swarming] Infer server from env This way a builder will no longer need to set its Swarming server with the "$recipe_engine/swarming" property. If the property is unset, the a build will default to launching tasks on the same Swarming server that the build is running on. Bug: 1148539 Change-Id: If72b10bef7b2dabb1b21482ea3752326bb2fce24 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3173593 Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Auto-Submit: Oliver Newman <olivernewman@google.com> Reviewed-by: Takuto Ikuta <tikuta@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.