commit | 5f23797390659ab5dc5efa0e561fa78697f50d18 | [log] [tgz] |
---|---|---|
author | Garrett Beaty <gbeaty@google.com> | Mon Jun 23 18:19:16 2025 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 23 18:19:16 2025 |
tree | 61fab6c956baf1d83319210a019a1041d7dadf8e | |
parent | b12105986eaa5c6bd8ad341ac108d6f862d24274 [diff] |
Revert "[snoopy] retry reporting errors in bcid reporter module" This reverts commit c34226a2b2e0c6cb64a49547356325a9ffab8ce5. Reason for revert: Necessary manual rolls weren't made, the build and chromiumos recipe rollers have been failing since Jun 18. Bug: b/411268646 Original change's description: > [snoopy] retry reporting errors in bcid reporter module > > Recipe-Manual-Change: build > Recipe-Manual-Change: chrome_release > Recipe-Manual-Change: chromiumos > Bug: b/411268646 > Change-Id: I13f3195fb3ffccce860b3933d5272d822b332067 > Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/6467814 > Commit-Queue: Dan Le Febvre <dlf@google.com> > Reviewed-by: Rachael Newitt <renewitt@google.com> Bug: b/411268646 Change-Id: I38ded08deab4aeba6a034913e0e9c037f9c12d4f Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/6663446 Commit-Queue: Ben Pastene <bpastene@chromium.org> Auto-Submit: Garrett Beaty <gbeaty@google.com> Owners-Override: Ben Pastene <bpastene@chromium.org> Reviewed-by: Ben Pastene <bpastene@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
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.