commit | 36a9f82370729f8c7f8a2eafabc077e35f26a9af | [log] [tgz] |
---|---|---|
author | Takuto Ikuta <tikuta@chromium.org> | Fri Oct 16 08:06:46 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 16 08:06:46 2020 |
tree | e8e204e15c9c0179586a5cd267aa5df3a66bc2f6 | |
parent | 0d7a977e5ce07f8d5b1f24269dac438851f9f721 [diff] |
[cas] inherit default_instance from SWARMING_SERVER envvar I think most (or all?) builders don't run task crossing swarming instances. So let me use the same swarming instance with task for cas by default instead of setting cas property for every builders. Bug: 1138100 Change-Id: I6145992bff958283a0b7bfd06644037b72e7c1d3 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2478422 Reviewed-by: Ye Kuang <yekuang@google.com> Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Auto-Submit: Takuto Ikuta <tikuta@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.