Google Git
Sign in
pigweed / infra / recipes / 05ab378ae6ac51ad785feb0394039e73245cdc29
commit05ab378ae6ac51ad785feb0394039e73245cdc29[log] [tgz]
authorRob Mohr <mohrr@google.com>Thu May 16 21:22:28 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu May 16 21:22:28 2024 +0000
tree54628d7eb695c20157d38d053f569a777af8e93e
parent62a8f67fd0ede1f8457fd64a18fd8468d04db103 [diff]
bazel_roller: Allow triggers from top-level

Allow triggers for bazel rollers to come from the top-level repository.
This allows weekly triggers for tool rollers to show in a console view
of the top-level repository as in
https://ci.chromium.org/p/pigweed/g/pigweed-roller/console.

Example failure at http://ci.chromium.org/b/8748199684281468785.

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