Google Git
Sign in
pigweed / infra / recipes / 3b2741042e828bad2a1450f8970df8a63199d476
commit3b2741042e828bad2a1450f8970df8a63199d476[log] [tgz]
authorRob Mohr <mohrr@google.com>Fri Mar 22 19:55:45 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Mar 22 19:55:45 2024 +0000
tree9b92616548bf935d7d877a3988975b5e5c97a40d
parent0e1fc309b4619545b9f75b6c29d919145611f048 [diff]
checkout: Set project from change details

Set the project in Change objects from the change_details result instead
of using the GerritChange object in the Buildbucket input. There were
several places where this result was not set properly in tests that
needed to be fixed.

Bug: b/328489817
Change-Id: I85b4b0efd0e42e82ef3436a3acd297ef7d690975
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/198730
Commit-Queue: Rob Mohr <mohrr@google.com>
Reviewed-by: Ted Pudlik <tpudlik@google.com>
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
39 files changed
tree: 9b92616548bf935d7d877a3988975b5e5c97a40d
  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.