Google Git
Sign in
pigweed / infra / recipes / 657415f293fdbe2bbbf775eadf9c253cdb09a667
commit657415f293fdbe2bbbf775eadf9c253cdb09a667[log] [tgz]
authorTed Pudlik <tpudlik@google.com>Mon Sep 23 23:25:02 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Sep 23 23:25:02 2024 +0000
tree2af28f93da28b40becfa2719d89b0fb8d8e3d6ce
parentbc70ea2e4d45819bbf17f890c34226f7279b911e [diff]
bazel: Use different RBE instances in CQ

Automatically determine the RBE instance to use in CI vs CQ. Because
this results in CQ using a dedicated instance, allow CQ jobs to write to
the cache. This should improve cache hit rates in CQ, especially for
subsequent patchsets of the same CL.

Also add a config option that allows enabling remote execution in CI and
CQ. (Although no repositories define the relevant Bazel config yet.)

Bug: 312215590
Change-Id: I1be80012a693669c41181ee63ebc2c4fda5136ab
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/237060
Reviewed-by: Rob Mohr <mohrr@google.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Ted Pudlik <tpudlik@google.com>
5 files changed
tree: 2af28f93da28b40becfa2719d89b0fb8d8e3d6ce
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. scripts/
  5. black ⇨ .cipd/black
  6. .editorconfig
  7. .gitignore
  8. .style.yapf
  9. AUTHORS
  10. cipd.ensure
  11. LICENSE
  12. OWNERS
  13. presubmit.sh
  14. pyproject.toml
  15. README.md
  16. recipes.py
README.md

Pigweed Recipes

This repository contains recipes for Pigweed.

A recipe is a Python script that runs a series of commands, using the recipe engine framework from the LUCI project. We use recipes to automatically check out, build, and test Pigweed and downstream projects using Pigweed in continuous integration jobs. The commands the recipes use are very similar to the ones you would use as a developer to check out, build, and test Pigweed in your local environment.

See go/pigweed-recipe-docs for complete documentation and a guide for getting started with writing recipes.

Getting the Code

The recommended way to get the source code is with git.

git clone https://pigweed.googlesource.com/infra/recipes

In most cases you will need a Chromium depot_tools checkout in your PATH as well.

git clone https://chromium.googlesource.com/chromium/tools/depot_tools ~/depot_tools
echo 'export PATH="$PATH:$HOME/depot_tools"' >> ~/.bashrc

Running Tests

./presubmit.sh runs three different sets of tests:

  • Recipe expectation tests (./recipes.py test train)
  • Formatting (./black --diff --check .)
  • Dependencies (.recipe_deps/fuchsia/scripts/cleanup_deps.py --check)

The formatting check will tell you what‘s wrong but not fix it. For that you need to run ./black .. Similarly, the dependencies check will tell you what’s wrong but you'll need to edit the files to fix issues.

If not using ./presubmit.sh you'll need to run ./scripts/ensure_black.sh before ./black is present.