commit | 3b1cb2ea044128062ffa57715df89b1efaaaba38 | [log] [tgz] |
---|---|---|
author | randymaldonado <randymaldonado@google.com> | Thu Mar 07 18:47:18 2024 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 07 18:47:18 2024 |
tree | b45cbc3f31a5988f697a5ef16de632029f1184ea | |
parent | 81fd7805b848baa52de454afdfcdc78f4c8550a1 [diff] |
[recipe-modules][buildbucket] Remove infra.swarming.priority hardcoding in schedule_request Add a test to ensure priority is being inherited from backend builds in schedule_request. Also update the test_api to accept backend_target values and default to chromium-swarming. This is crucial for tests that use task backend since having a swarming target is requried for accessing any swarming specific fields in build.infra.backend. Bug: 326592434 Change-Id: I0dfc77a239b6875b6c5f8a48a429fbf86ca72aee Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/5352809 Auto-Submit: Randy Maldonado <randymaldonado@google.com> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org> Commit-Queue: Randy Maldonado <randymaldonado@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.