| commit | 284f068413e195b729229997e144439bf26994a3 | [log] [tgz] |
|---|---|---|
| author | Oliver Newman <olivernewman@google.com> | Wed Sep 01 00:05:30 2021 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 01 00:05:30 2021 |
| tree | 4e0c9be2ff8238764a00fedcdcc81e6581abaa42 | |
| parent | a3f37fc43c210b3991121e63ab0b9adf87d6a9df [diff] |
[json] Sort test data keys Python 2 and 3 use different iteration ordering for dictionaries (and sets) which causes expectation file differences between the two versions for mock data that doesn't use `sort_keys`. Recipe-Nontrivial-Roll: build Recipe-Nontrivial-Roll: chrome_release Recipe-Nontrivial-Roll: chromiumos Recipe-Nontrivial-Roll: fuchsia Recipe-Nontrivial-Roll: infra Change-Id: I2cea4a8269bf5b3a6721a6a78371eb1713fb0329 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3134182 Commit-Queue: Oliver Newman <olivernewman@google.com> Reviewed-by: Yiwei Zhang <yiwzhang@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.