Roll recipe dependencies (trivial).

This is an automated CL created by the recipe roller. This CL rolls
recipe changes from upstream projects (infra, recipe_engine) into this repository.

The build that created this CL was
https://ci.chromium.org/b/8682308012713083089

infra:
https://chromium.googlesource.com/infra/infra.git/+log/d7cf9da2d61ce24cf40548c0af5b43f94313f0fa~..b895a9bed7f0a572e8ca42a196a912eb03b47476
  d7cf9da (chromium-autoroll@skia-public.iam.gserviceaccount.com)
      Roll luci-py from 89af5cfdf74e to f5175465bf02 (1 revision)
  14646cb (chromium-autoroll@skia-public.iam.gserviceaccount.com)
      Roll chromiumos/config from 62940545bc56 to e876e9c767d6 (1 rev...
  b895a9b (chromium-autoroll@skia-public.iam.gserviceaccount.com)
      Roll chromiumos/infra/proto from 6163151ee625 to a93260e47544 (...

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py.git/+/70bb072f0c4b15194060aafbafe3e0ce79a0387f
  70bb072 (chromium-autoroll@skia-public.iam.gserviceaccount.com)
      Roll CAS Client from 3df8f33fc497 to af8531728740

Please check the following references for more information:
- autoroller, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#autoroller
- rollback, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#rollback
- cross-repo dependencies, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/cross_repo.md

Use https://goo.gl/noib3a to file a bug.

Recipe-Tryjob-Bypass-Reason: Autoroller
Ignore-Freeze: Autoroller
Bugdroid-Send-Email: False
Change-Id: I1d83d3d526eca695eea13ff432342bf5dc42e478
2 files changed
tree: 0e41a89987b07c21030bedb22ccdfc4dbf73ed5e
  1. generated/
  2. infra/
  3. recipes/
  4. repos/
  5. .gitignore
  6. main.star
  7. README.md
README.md

LUCI Configuration

This repo holds all the configuration for LUCI, the CI system Gerrit uses. You can find recent verification runs and logs at https://ci.chromium.org/ui/p/gerrit/builders.

Concepts

  • Recipe: a python script to verify a change, and a test for that verification
  • Builder: a recipe configured to run on a specific machine type
  • CQ Group: a watcher that triggers on new votes/patchsets on the specified repo+refs
  • CQ Tryjob Verifier: combines a CQ group with a builder to run a recipe when a new vote or patchset comes in

Layout

  • /main.star: overall starlark configuration for the entire host. It is also executable to generate the config data
  • /repos/*.star: repo-specific starlark configuration for builders, CQ groups, CQ tryjob verifiers, etc
  • /recipes/recipes/*.py: recipes for testing a change based on the repo
  • /recipes/recipes.py: executes recipe tests and compares/generates expected JSON goldens. 100% coverage is expected.
  • /recipes/recipe_modules/: dependencies shared by modules
  • /recipes/*.expected/*.json: expected commands executed by the recipe
  • /infra/config/recipes.cfg: versions and URLs of external recipe dependencies

Prerequisites

  • lucicfg - CLI tool to generate the configuration from the starlark scripts. To install, clone depot_tools.
  • python - Python 3, used to execute recipes.

Imporant commands

Regenerate config data after making changes (lucicfg):

$ ./main.star

Run recipe tests (python):

$ recipes/recipes.py test run

Update recipe test goldens (python):

$ recipes/recipes.py test train

Documentation