commit | 6bb449da37f04e02e60a27c910d491c851050191 | [log] [tgz] |
---|---|---|
author | Robert Iannucci <iannucci@chromium.org> | Tue Jun 25 22:46:57 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Jun 25 22:46:57 2019 |
tree | 47072f317f55cc2f75a328360ae6e0fabf98b998 | |
parent | d13e90544ecc6da9fb394c5c61e927c0fe03ec65 [diff] |
[stream/luci] Combine stdout/stderr for now. This is the current behavior under @@@annotations@@@, and so we'll preserve it for now to avoid ruffling feathers. We'll be able to undo this once the LogDog viewer gains the ability to show multiple streams again. R=tandrii@chromium.org Bug: 910369 Change-Id: Ic1cf653421570083cc9955223b1d42f53bcbba5f Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1677366 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@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.