| commit | bb01260dc91d33aa60051a3790a1abc67d26334c | [log] [tgz] |
|---|---|---|
| author | Alexander Schulze <alexschulze@chromium.org> | Fri Jul 01 23:38:00 2022 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 01 23:38:00 2022 |
| tree | 334782161727bbe6ffa57d51c03ae6385ca952bc | |
| parent | 2fdd5ba812beb59d941d96e5920bda658764d9f9 [diff] |
Revert "[file] Add fail_silently to copy and copytree" This reverts commit d14718e984d2b7b539f8f9c8bec3215807c0a681. Reason for revert: We are now validating the existence of the files in the upstream recipe (https://crrev.com/c/3736104), and do not require `skip_empty_sources` in the files api anymore. Original change's description: > [file] Add fail_silently to copy and copytree > > Currently, `file.copy` and `file.copytree` both fail if the source path does not exist. This change introduces an extra attribute `skip_empty_source` to ignore these errors. > > Bug: 1329786 > Change-Id: I33080d4597ba70ac8a008979ac8b7315c2ce1c32 > Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3673077 > Auto-Submit: Alexander Schulze <alexschulze@chromium.org> > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Alexander Schulze <alexschulze@chromium.org> Bug: 1329786 Change-Id: I0bab234049b4f116169c2fb5939c07215b2e0b77 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3738141 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Alexander Schulze <alexschulze@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.