Google Git
Sign in
pigweed / infra / recipes / 8c66f25ae6235c974286383b6bb8417613d218bf
commit8c66f25ae6235c974286383b6bb8417613d218bf[log] [tgz]
authorRob Mohr <mohrr@google.com>Thu Jun 06 15:08:43 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jun 06 15:08:43 2024 +0000
tree8dc9a44dfa4fe6c675238ca100583d9351e9df33
parent1ba9cd2e235b466da5d3a112d3d2aa28b4c00c79 [diff]
checkout: Apply changes to WORKSPACE rules

Apply triggering changes to git_repository() rules in WORKSPACE files.

Tested with led: http://ci.chromium.org/b/8745931961123789713.

Bug: b/323009830
Change-Id: Icd120e1fe81f8f3b0d0d977a436e9b902bc32377
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/214012
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Rob Mohr <mohrr@google.com>
Reviewed-by: Oliver Newman <olivernewman@google.com>
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
86 files changed
tree: 8dc9a44dfa4fe6c675238ca100583d9351e9df33
  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.