| commit | 26cd5483c9c3af4520d992522798dc38f404e5a1 | [log] [tgz] |
|---|---|---|
| author | Stephanie Kim <kimstephanie@google.com> | Fri Jan 20 00:07:35 2023 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 20 00:07:35 2023 |
| tree | 49d682012bc1a85d4445731d8e1aca0f36a45185 | |
| parent | 7ec46d46ce021b3b17526c5eb7a6492d385a02ea [diff] |
Create luci_analysis recipe_module
This copies over the weetbix module from tools/build.git with the extra
fluff around QueryFailureRate removed.
In the previous weetbix module [0], query_failure_rate received an input of Test objects, instead of list of {'testId':str, 'variantHash': str}.
It also did some extra formatting to return a list of FailureRateAnalysisPerSuite objects.
Now, query_failure_rate will be a
simple wrapper around the QueryFailureRate RPC call and return a list of
protos, like the other methods in this module. The recipes in tools/build will be updated to create their own FailureRateAnalysisPerSuite objects with the returned list of protos.
[0]: https://source.chromium.org/chromium/chromium/tools/build/+/main:recipes/recipe_modules/weetbix/api.py;l=1;drc=fb2f0edd55ee2c6711efa2117f86637207230722
Bug: 1392220
Change-Id: Ide19069c57264fd34192cfb58ff96f63d8dc6889
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/4179291
Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Stephanie Kim <kimstephanie@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.