| commit | f28ac0ab20025138a3f46845de09d625960c2a97 | [log] [tgz] |
|---|---|---|
| author | Chan Li <chanli@chromium.org> | Tue Sep 21 22:57:22 2021 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 21 22:57:22 2021 |
| tree | f472162a38b1c81e45cd043a7be2db2d96eff969 | |
| parent | 63c685b8721140415e55e8756a5026ff5349dfc6 [diff] |
Reland "[recipe-py] expose resultdb info in LUCI_CONTEXT" This is a reland of crrev.com/c/3153276 with a fix: update token should not be hidden in api.context.luci_context. In the previous CL I hid resultdb update_token because I thought it will be revealed in execution details. But it turned out that the LUCI_CONTEXT file will be updated by api.context.luci_context[1] which means update_token will be lost. Also [2] controls what sections of LUCI_CONTEXT to show in execution details so update token will not be leaked. [1] https://source.chromium.org/chromium/_/chromium/infra/luci/recipes-py/+/17c88f22dfef427f9e085e2e7078cbeaaca5be6c:recipe_engine/internal/engine.py;l=810;drc=ffe17790c212701a06373ab9fd0ce3a54dab9173 [2] https://source.chromium.org/chromium/_/chromium/infra/luci/recipes-py/+/17c88f22dfef427f9e085e2e7078cbeaaca5be6c:recipe_engine/internal/engine.py;l=1024;drc=ffe17790c212701a06373ab9fd0ce3a54dab9173 Bug: 1245438 Change-Id: I07aa291594699a6bb6105ac6ce5b29b93782144a Recipe-Manual-Change: fuchsia Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3162665 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@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.