| commit | 742a272b323d92aa97865daa3b806a8ee665eeb2 | [log] [tgz] |
|---|---|---|
| author | Ben Pastene <bpastene@chromium.org> | Fri Jul 17 22:26:55 2020 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 17 22:26:55 2020 |
| tree | c74a9d84d6b2dbef89e510f6273e97d51aab3161 | |
| parent | c1b7a3041fc0dedb1ee46bcb206e0b048ce7a20f [diff] |
Revert "[raw_io] Make output_dir lazy." This reverts commit c1b7a3041fc0dedb1ee46bcb206e0b048ce7a20f. Reason for revert: "No such file or directory" on some win builds See crbug.com/1085016#c36 Reverting first, asking questions later... Original change's description: > [raw_io] Make output_dir lazy. > > This will allow recipes to continue using output_dir but without > exploding their memory usage. > > R=​bpastene@chromium.org, yiwzhang@google.com > > Bug: 1085016 > Recipe-Nontrivial-Roll: build > Recipe-Nontrivial-Roll: build_limited_scripts_slave > Recipe-Nontrivial-Roll: chrome_release > Change-Id: I2a569341dad3a1e14f44b57f3e91cd1b769ea7b5 > Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2303595 > Auto-Submit: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Ben Pastene <bpastene@chromium.org> > Reviewed-by: Ben Pastene <bpastene@chromium.org> > Reviewed-by: Yiwei Zhang <yiwzhang@google.com> TBR=iannucci@chromium.org,bpastene@chromium.org,yiwzhang@google.com,infra-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: I966d10a9fde33eb5dc5e73efd2ddb63997c5558c No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1085016 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2304261 Reviewed-by: Ben Pastene <bpastene@chromium.org> Commit-Queue: Ben Pastene <bpastene@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.