| commit | 2d4b5456534f32afc385663a5395273759009f18 | [log] [tgz] |
|---|---|---|
| author | Benjamin Shai <bshai@google.com> | Wed Apr 17 19:46:11 2024 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 17 19:46:11 2024 |
| tree | a5d82664afd5fc8aee77372dcb98cd7299f56b73 | |
| parent | a8b4a93c425be92ec85c4df82fd3798aef3245bc [diff] |
recipes-engine: add profile command Add a profile command that operates much the same way that the debug command does, taking in a test name and profiling that test. This uses cProfile to create profiler output, and supports running in stdout mode as well as file mode. BUG=None TEST=manual Change-Id: I1a696c2d0c59e7da76564d13ef44d6c9f615a4a9 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/5458722 Reviewed-by: Rob Mohr <mohrr@google.com> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Benjamin Shai <bshai@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.