Google Git
Sign in
pigweed / infra / recipes / 62a8f67fd0ede1f8457fd64a18fd8468d04db103
commit62a8f67fd0ede1f8457fd64a18fd8468d04db103[log] [tgz]
authorRob Mohr <mohrr@google.com>Thu May 16 21:20:21 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu May 16 21:20:21 2024 +0000
tree5c6bb102f2e310e4445835e6970da8c7d22afbe3
parent68a7ba2647bf37eb03a39c2cff5eaff36770b06f [diff]
save_logs: Ignore nested JSON files

Ignore arbitrarily nested JSON files when saving logs. Since they still
provide some value for env setup, continue to include JSON files under
'cipd'.

This will make builds like http://ci.chromium.org/b/8747764136503746385
not spend nearly so much time copying big JSON files around (see step
5.4.53).

Also sort the list of patterns.

Change-Id: I0683fc2f01719001f33e80c6ed79b85a66126b1b
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/210233
Commit-Queue: Rob Mohr <mohrr@google.com>
Reviewed-by: Ted Pudlik <tpudlik@google.com>
Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
23 files changed
tree: 5c6bb102f2e310e4445835e6970da8c7d22afbe3
  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.