Revert "[TurboCI] expose turboci section of LUCI_CONTEXT" This reverts commit ce25b7d290014f59a00d29ab058a1f12ef5b83fb. Reason for revert: No longer needed. We've just changed `turboci` CLI to auto-inject the TurboCI token from the context, so callers don't need to discover it themselves. Original change's description: > [TurboCI] expose turboci section of LUCI_CONTEXT > > So that callers can get the token and attach it to TurboCI requests > > Bug: b/449231255 > Change-Id: I1d71e3cedb35699552df6c9e8b09b5c0fb480f21 > Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/7813945 > Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> > Commit-Queue: Chan Li <chanli@chromium.org> Bug: b/449231255 Change-Id: I9e63531601af09daad946adc5d231031ff219790 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/7823968 Commit-Queue: Chan Li <chanli@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Bot-Commit: rubber-stamper@appspot.gserviceaccount.com <rubber-stamper@appspot.gserviceaccount.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.