Google Git
Sign in
pigweed / infra / recipes / 4763ec0f72deeb3012312bac5d9845c26e9b7f5a
commit4763ec0f72deeb3012312bac5d9845c26e9b7f5a[log] [tgz]
authorslliu <slliu@google.com>Tue Aug 06 22:38:26 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Aug 06 22:38:26 2024 +0000
treee6c15f469993f81d992bf5e1c9ec0e2c7af3cd34
parent05925089bece2f9f62a6ec3e3adad90d3da8b2de [diff]
multi_roller: Add ready_labels option

Bug: 338115792

The ready_labels multi_roller option will allow the user to specify
which labels will indicate when a sub-roll is ready to submit.

Change-Id: I36d9d8884bb486eb18b85d1ad02a1d97eb11c211
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/227181
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Reviewed-by: Rob Mohr <mohrr@google.com>
Commit-Queue: Samuel Liu <slliu@google.com>
9 files changed
tree: e6c15f469993f81d992bf5e1c9ec0e2c7af3cd34
  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.