Google Git
Sign in
pigweed / infra / recipes / 2eaecf99b02addf5a7ef7281caffa80ced4d2023
commit2eaecf99b02addf5a7ef7281caffa80ced4d2023[log] [tgz]
authorRob Mohr <mohrr@google.com>Tue Apr 16 17:20:33 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 16 17:20:33 2024 +0000
tree943096808abad83c2564c2938f2dd909132b983a
parentac48ca68b67b03039f7e0deada05dbce7c43f289 [diff]
pw_presubmit, cipd_upload: Support manifests

Change pw_presubmit to check for 'builder_manifest.json' files in the
build directory. If one exists, parse it and look for CIPD manifests.
Upload CIPD packages based on the contents of those CIPD manifests.

Bug: b/332357274
Change-Id: I210e462cb1056fe90d2383da5a8c574879f5d4c1
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/203653
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>
25 files changed
tree: 943096808abad83c2564c2938f2dd909132b983a
  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.