Google Git
Sign in
pigweed / infra / recipes / d980ddbc6894988ae80c296940e9a4e6953886e9
commitd980ddbc6894988ae80c296940e9a4e6953886e9[log] [tgz]
authorRob Mohr <mohrr@google.com>Wed Jan 17 03:19:29 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jan 17 03:19:29 2024 +0000
tree45c33f417ec332d621809b28284168dc1d22288a
parent1e644a6de3a96a0814e705568b58dd0a80446ef9 [diff]
roll_util: Handle accounts without emails

Handle Gerrit accounts that don't have emails without terminating.

Bug: b/320579863
Change-Id: I7d16300ef05b8e6f112503070e576b745529b7f3
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/188130
Reviewed-by: Shuvra Dutta <shuvro@google.com>
Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com>
Commit-Queue: Shuvra Dutta <shuvro@google.com>
Commit-Queue: Rob Mohr <mohrr@google.com>
1 file changed
tree: 45c33f417ec332d621809b28284168dc1d22288a
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. scripts/
  5. black ⇨ .cipd/black
  6. .gitignore
  7. .style.yapf
  8. AUTHORS
  9. cipd.ensure
  10. LICENSE
  11. OWNERS
  12. presubmit.sh
  13. pyproject.toml
  14. README.md
  15. 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.