Google Git
Sign in
pigweed / infra / recipes / f64bcb5bd38960a7bf99815a2969fb05161ffb1b
commitf64bcb5bd38960a7bf99815a2969fb05161ffb1b[log] [tgz]
authorTed Pudlik <tpudlik@google.com>Tue Dec 17 19:38:18 2024 -0800
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Dec 17 19:38:18 2024 -0800
tree9cdb636bbe520dd99aea415c3487c9b21af75e39
parent0e240ee4cbf34ccf89127c07f001948b08544574 [diff]
bazel: By default, don't download artifacts

Most builders that do `bazel build` are simply verifying that the build
succeeds, and don't need to download the output artifacts. I think this
was set to True as a mistake in http://pwrev.dev/241252; that CL set the
download_all_artifacts kwarg to two different values in BazelRunner and
BazelApi.

Bug: 384790659
Change-Id: I9c5c94e7d348f8d8cdbc27d8c6a7c576486ddf84
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/255106
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com>
Pigweed-Auto-Submit: Ted Pudlik <tpudlik@google.com>
Reviewed-by: Rob Mohr <mohrr@google.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
2 files changed
tree: 9cdb636bbe520dd99aea415c3487c9b21af75e39
  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.