| commit | f3cd3581d21f3d3e719096839f3c0186c001d6be | [log] [tgz] |
|---|---|---|
| author | Vadim Shtayura <vadimsh@chromium.org> | Fri Aug 28 02:09:52 2020 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 28 02:09:52 2020 |
| tree | e286b41eb29f9a3ca06553b67653d733b49ec3ee | |
| parent | 26ed4c400c30e84a6da7363b880e87be56b4e4b1 [diff] |
[swarming] Use builder's realm when launching ResultDB tasks. This will allow to experiment with ResultDB-enabled tasks launched from non-realm-enabled builds (i.e. almost all of them). Be careful to use this *only* for ResultDB tasks. Using it by default everywhere will blow everything up, since Swarming will reject such tasks because it has no realm ACLs configured yet. Bug: 1122808 R=nodir@chromium.org, yekuang@google.com, jwata@google.com Change-Id: I7f9fd381b1e800303091c3f4535d09715971b26a Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2380851 Reviewed-by: Ye Kuang <yekuang@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Junji Watanabe <jwata@google.com> Commit-Queue: 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.