Google Git
Sign in
pigweed / infra / recipes / 5d71a6e7a62922175b7368e1b9734d9c64e0b7f6
commit5d71a6e7a62922175b7368e1b9734d9c64e0b7f6[log] [tgz]
authorRob Mohr <mohrr@google.com>Thu Apr 25 19:19:10 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Apr 25 19:19:10 2024 +0000
tree4d957d8dd4441f052b4bb4e692737ad8b7423b28
parent4c9b032d188bf2a9cebe9ae948ad5e5360ba1ae1 [diff]
bazel: Use bazelisk to get bazel

Also, add post-process checks and drop expectations for this module.

All builders using the 'bazel' recipe have explicit 'cipd_json_path'
properties set, so this should be a no-op.

Bug: b/336617748
Change-Id: If94ea446f626cf70cd763b646f66d7506898db22
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/206154
Reviewed-by: Oliver Newman <olivernewman@google.com>
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Commit-Queue: Rob Mohr <mohrr@google.com>
6 files changed
tree: 4d957d8dd4441f052b4bb4e692737ad8b7423b28
  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.