| commit | d5e316deefc54c4bcca73a164235f02ef8bd4e78 | [log] [tgz] |
|---|---|---|
| author | Ben Pastene <bpastene@chromium.org> | Fri Oct 02 23:34:58 2020 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 02 23:34:58 2020 |
| tree | 3287c114ce2b00ed510cc6f0647e1344252f0adb | |
| parent | 6126bc2f1092567bb3b0d96f0381330ba01ead75 [diff] |
Add a json.input log link to every swarming.trigger() invocation. Right now, it's difficult to determine the full set of inputs to a golang trigger invocation. With this, we can see what exactly is passed to the swarming client. See example led build with this patch applied: https://ci.chromium.org/swarming/task/4f0405a119474310 Recipe-Nontrivial-Roll: build Recipe-Nontrivial-Roll: fuchsia Recipe-Nontrivial-Roll: build_limited_scripts_slave Bug: 1132206, 894045 Change-Id: Ica7915d4d8f1b551bd5e37b5503aeb03d74ef0de Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2446821 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Ben Pastene <bpastene@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.