Google Git
Sign in
pigweed/infra/recipes/9cc019891eb263ae32761e09220c804f9c43a6ee
commit
9cc019891eb263ae32761e09220c804f9c43a6ee
[log]
author
Rob Mohr <mohrr@google.com>
Tue May 12 13:01:29 2026 -0700
committer
CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Tue May 12 13:01:29 2026 -0700
tree
609d693b81a5665e61a1786b60da4ff26e9a48e9
parent
38d643173f8a1f2c1989e1a19acb6eddbd7f4912 [diff]
Revert "roller: Support matching branches"

This reverts commit 38d643173f8a1f2c1989e1a19acb6eddbd7f4912.

Reason for revert: breaking all rollers

Original change's description:
> roller: Support matching branches
>
> When triggering off a branch name that appears in both the submodule and
> the top-level project, and when match_triggering_branch is set, roll
> into that branch on the top-level project.
>
> Also remove some earlier code that was trying to do something similar.
>
> Bug: b/509549918
> Change-Id: I9d74e3f420213b02875df823f4b67e0e4bdf674e
> Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/409294

TBR=mohrr@google.com,pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com,afoxley@google.com,android-build-ayeaye@system.gserviceaccount.com

No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: b/509549918
Change-Id: I1a59a65e15515a38949408c5783ad029d78e67a9
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/409675
15 files changed
tree: 609d693b81a5665e61a1786b60da4ff26e9a48e9
  1. infra/
  2. recipe_modules/
  3. recipe_proto/
  4. recipes/
  5. scripts/
  6. .aiderignore
  7. .editorconfig
  8. .gitignore
  9. .style.yapf
  10. AUTHORS
  11. GEMINI.md
  12. LICENSE
  13. OWNERS
  14. presubmit.sh
  15. pyproject.toml
  16. README.md
  17. recipes.py
  18. shac.ensure
  19. shac.star
  20. shac.textproto
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.