commit | 409188f97be0a541f7b7094e7113014c684926b7 | [log] [tgz] |
---|---|---|
author | Oliver Newman <olivernewman@google.com> | Fri Oct 23 17:42:15 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 23 17:42:15 2020 |
tree | 8277599c1e8bcd79ea482eee29baabb8c095ed2c | |
parent | 3b02f8181024472eee02fcb55fd7f9291accbf94 [diff] |
[test] Make expectation file filter more strict Turns out that some recipe repositories use custom a expectation file format for testing their resource scripts (see http://crrev.com/c/2493113). We don't want to consider those expectation files to be recipe expectation files, because then `recipes.py test` will consider them to be unused because of http://crrev.com/c/2491609. So make the expectation file filter more strict, only looking for expectation files in the root of *.expected directories and only looking for *.expected directories in the root recipes dir along with the 'run', 'examples', and 'tests' subdirectories of recipe modules. Change-Id: I917fc2157224b6106da25a0f61c06de234b98aaa Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2495283 Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Commit-Queue: Oliver Newman <olivernewman@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.