| commit | 619324050cd76c770cce159952b9625814a57ff0 | [log] [tgz] |
|---|---|---|
| author | Ben Pastene <bpastene@chromium.org> | Tue Jan 25 19:29:54 2022 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 25 19:29:54 2022 |
| tree | a43333ada943de8506960a9c625191024ffb887d | |
| parent | a476355d81d68d946bb2ab2b9431d648e7ad2167 [diff] |
Add 'resultdb_info' fields to default swarming JSON in recipe tests Nearly every chrome test now has rdb enabled, and crrev.com/c/3383909 will start changing build displays based on these fields. So add them to the default JSON so recipe tests have test JSON that's more representative of the JSON in real builds. Recipe-Nontrivial-Roll: build_limited Recipe-Nontrivial-Roll: fuchsia Recipe-Nontrivial-Roll: chromiumos Recipe-Nontrivial-Roll: build Bug: 1135718 Change-Id: If7053cf6de2f9c1472144f6ec12c88d1d0de1e69 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3387948 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.