| commit | 9739dd145b64ef8a9e33d0a4a5e25e8c516d83d4 | [log] [tgz] |
|---|---|---|
| author | George Engelbrecht <engeg@google.com> | Wed Aug 14 22:54:33 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed Aug 14 22:54:33 2019 |
| tree | c8759df4503bc0a3710d8d54e68a73c57db90630 | |
| parent | dbc1acf1456ba2041808ab5ac96d2bbe5ebdbf49 [diff] |
Make set_worse_status not crash on None status We can't call set_worse_status without having set a status first. This change makes it so if one hasn't been set, it will simply use the status we had intended to compare. BUG=993111 Change-Id: Id3e2ca1f2f8874f5d1d0ef93ffb0688ef238cfde Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1750110 Commit-Queue: George Engelbrecht <engeg@google.com> Reviewed-by: George Engelbrecht <engeg@google.com> Reviewed-by: Robbie Iannucci <iannucci@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.