commit | 85de6e48a32889aa7dd9ea7e38f459873a930f30 | [log] [tgz] |
---|---|---|
author | Garrett Beaty <gbeaty@chromium.org> | Fri Jun 05 00:52:43 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 05 00:52:43 2020 |
tree | 454e128856d53af8925d0c529bbe5cf2235dbe6b | |
parent | 85c3458f65122aec9e09d17f0b10960bfff5b701 [diff] |
Add swarming.ensure_client(). In order to be able to get the swarming client ready in parallel with performing operations leading up to its use, there should be a public method that can be called that results in the client being fetched. Currently, all of the public methods either do not cause the client to be fetched, actually use the client or is a context manager, which is awkward to trigger a greenlet for. Change-Id: I18e28076448f657e3860133c6b3dbbd701bbbf60 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2230780 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Auto-Submit: Garrett Beaty <gbeaty@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.