Google Git
Sign in
pigweed / infra / recipes / e3ca26960496e0153633115adc28c3ffd0eb9a8d
commite3ca26960496e0153633115adc28c3ffd0eb9a8d[log] [tgz]
authorRob Mohr <mohrr@google.com>Tue Jul 23 14:54:28 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jul 23 14:54:28 2024 +0000
tree7d862f52e9e9d1dbb45aabf67ab6f5d90f42ac67
parent3866c5b9f0fbd5ac41ba9c5d8ca17ff972145dbe [diff]
bazel, checkout: Rebase git_repository() changes

Rebase changes to repos that are pulled into the build using Bazel
git_repository() rules. Then use those changes from Bazel by adding
--override_repository arguments.

Bug: b/349670891
Change-Id: Ie7e32504d0c6a64b945071cb0134eaf57bfb556a
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/223993
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Ted Pudlik <tpudlik@google.com>
Commit-Queue: Rob Mohr <mohrr@google.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
14 files changed
tree: 7d862f52e9e9d1dbb45aabf67ab6f5d90f42ac67
  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.