Roll CAS Client from 3df8f33fc497 to af8531728740 https://chromium.googlesource.com/infra/infra.git/+log/3df8f33fc497..af8531728740 2026-05-08 tbain@google.com Give role/turboci.workplanCreator to turbo-ci-team 2026-05-08 bjoyce@google.com Add support for new hyperdisk types 2026-05-08 chromium-autoroll@skia-public.iam.gserviceaccount.com Roll luci-go from edaa1ba51c8e to caa858058dd0 (1 revision) 2026-05-08 gregorynisbet@google.com [nodeclassifier] Replace google.protobuf.Struct with ParameterStruct 2026-05-08 chromium-autoroll@skia-public.iam.gserviceaccount.com Roll luci-go from de0bc0c40bb3 to edaa1ba51c8e (1 revision) 2026-05-08 gregorynisbet@google.com Change the YAML library that we're using. 2026-05-08 gregorynisbet@google.com [nodeclassifier] Create internal YAML wrapper 2026-05-08 otabek@google.com recovery: ignore firmware read failure on Flex devices 2026-05-08 kimjae@google.com Conditionally set GBB flags in Android install 2026-05-08 chromium-autoroll@skia-public.iam.gserviceaccount.com Roll luci-go from e7093225bb39 to de0bc0c40bb3 (1 revision) 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: I45c93e31811ecbca1c6c987b2ff44bd01e20c459 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/7833930 Commit-Queue: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: chromium-autoroll@skia-public.iam.gserviceaccount.com <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.