commit | ba4a4b2d4f1f41483b2da98854f648727b4aecdb | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Mon Nov 29 11:54:34 2021 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Nov 29 11:54:34 2021 |
tree | ba9d165b4083539ef88a127a28b4e712ee348835 | |
parent | 6d57d876daf8c71cf6d7c48dade968f7d46244d0 [diff] |
Roll CAS Client from 83708e8181ac to 7422359d33c6 https://chromium.googlesource.com/infra/infra.git/+log/83708e8181ac..7422359d33c6 2021-11-29 chromium-autoroll@skia-public.iam.gserviceaccount.com Roll luci-py from 6d2f3934b6d4 to 8d37831e8af5 (1 revision) 2021-11-29 chromium-autoroll@skia-public.iam.gserviceaccount.com Roll chromiumos/infra/proto from 76674f60ba14 to 600d719eb026 (1 revision) 2021-11-29 chromium-autoroll@skia-public.iam.gserviceaccount.com Roll chromiumos/config from 403b5120c19e to 25c6bcac5a2c (1 revision) 2021-11-29 chromium-autoroll@skia-public.iam.gserviceaccount.com Roll luci-go from 1a7894976e50 to 3cbf7ac670c6 (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 tikuta@chromium.org,jwata@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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: tikuta@chromium.org,jwata@google.com Change-Id: Idd2859488dbbac4a4f7cf670d0aee7585ca13013 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3306197 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.