commit | 7e3be54729659656666407fddc6a29906f1662f8 | [log] [tgz] |
---|---|---|
author | Takuto Ikuta <tikuta@chromium.org> | Fri Oct 16 10:35:56 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 16 10:35:56 2020 |
tree | bf053851e88618bc382b78825c7154d668523e99 | |
parent | 36a9f82370729f8c7f8a2eafabc077e35f26a9af [diff] |
[cas] use os.environ to get SWARMING_SERVER envvar This is fix for https://crrev.com/c/2478422 context recipe modules is used to set envvar for recipes steps, but not for getting outer environment. This CL uses os.environ in real execution instead. Bug: 1138100 Change-Id: Icaf3a6fab79c9f6c4593792d76e51536eb6e24ef Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2479342 Commit-Queue: Ye Kuang <yekuang@google.com> Reviewed-by: Ye Kuang <yekuang@google.com> 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.