commit | 4f12504d84f212988adacdbf413051e1aaf5f61d | [log] [tgz] |
---|---|---|
author | Robert Iannucci <iannucci@chromium.org> | Sat May 25 02:00:02 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Sat May 25 02:00:02 2019 |
tree | 515b0b9a38e60d92d2c514980f2777000839d7ae | |
parent | 16a26b8a4218fab4320f63c4ddd27fb6471bcc55 [diff] |
Remove ability to set callback on nesting steps. Nothing got the chance to use this (hopefully). Also beef up the documentation around `api.step.nest`. This makes it so that the nest function just directly yields the StepPresentation... which is the only object that anyone would care about anyhow :). Unfortunately, because all the existing code expects a StepData-containing-a-StepPresentation to be yielded, we have to add an awkward proxy object around the presentation to avoid needing to update all code in the ecosystem. R=tandrii@chromium.org Bug: 910369 Change-Id: I26f27d9499e43cbb532f9b176b8a9dd6d7f2251c Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1629438 Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@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.