commit | 3f64ba05d329bb41bc8b651d07b7b7f3c1bf4135 | [log] [tgz] |
---|---|---|
author | Robert Iannucci <iannucci@chromium.org> | Mon Jun 03 22:40:11 2019 |
committer | Robbie Iannucci <iannucci@chromium.org> | Mon Jun 03 22:40:11 2019 |
tree | c4e5c4632c88e54b42112fbf1b7b8da13c3e5a09 | |
parent | 94a299a13fceebfccc56e692e46b7daa16903b07 [diff] |
Fix manifest link. This was broken in a previous CL where I didn't realize that active_step returning the entire internal object ActiveStep was actually used. This adds a small method to expose the required functionality (set_manifest_link) instead of exposing the internal object. R=tandrii@chromium.org Bug: 910369 Recipe-Tryjob-Bypass-Reason: Fixing regression that breaks roll tryjobs Change-Id: I3dfc58d6def2b9e2979da2f5a5f7234bc665d2d0 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1641539 Commit-Queue: 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.