Google Git
Sign in
pigweed / infra / recipes / e11f0971bc05c3e1f06c6f75d30df41348c0b95a
commite11f0971bc05c3e1f06c6f75d30df41348c0b95a[log] [tgz]
authorRob Mohr <mohrr@google.com>Thu Aug 15 02:11:14 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Aug 15 02:11:14 2024 +0000
tree727f8f6662b2cb768ddb6ac220610d4d87836f34
parent9c76226ab107a3fb67cdc382d2d2ac5bba7b52b7 [diff]
submodule_roller: Split submodule-specific parts

Move submodule-specific parts to a separate function. This is a step
towards making the RunSteps() functions in each roller look more or less
the same, so they can be merged in the future.

No changes to expectation files.

Bug: b/341756093
Change-Id: If3e691679cde549d35a380c6379f1b2a6a476879
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/229716
Commit-Queue: Rob Mohr <mohrr@google.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Danielle Kay <danikay@google.com>
2 files changed
tree: 727f8f6662b2cb768ddb6ac220610d4d87836f34
  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.