commit | 07e4e55ddf716d02eb031c1e165239265431026d | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Sep 18 00:38:21 2025 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Sep 18 00:38:21 2025 |
tree | dd27d0b085e00ce1cef2f77ba8602763fa0f3e3d | |
parent | af73739e9bf032b145ac29ef72f98b1498543429 [diff] |
Roll CAS Client from 8542fcedab33 to 6645da847edf https://chromium.googlesource.com/infra/infra.git/+log/8542fcedab33..6645da847edf 2025-09-17 boris.lok@cienet.corp-partner.google.com satlab: [Feature] show `testlab` status. 2025-09-17 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). 2025-09-17 gregorynisbet@google.com Increase timeout for satlabrpc tests 2025-09-17 chromium-autoroll@skia-public.iam.gserviceaccount.com Roll luci-go from a707fd00fdd3 to 5b06a95669e6 (1 revision) 2025-09-17 mattbubernak@google.com CTPv2 Support AL -> AL multi DUT provisioning 2025-09-17 chromium-autoroll@skia-public.iam.gserviceaccount.com Roll luci-go from 5f577af97a58 to a707fd00fdd3 (2 revisions) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cas-recipes-py Please CC iannucci@google.com,peepsi-tod-team@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: iannucci@google.com Change-Id: I41547d2dcc48e5369816373c95145d4b4d0e261f Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/6961224 Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.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.